Related
1. whats rooting ?
2. whats recovery for?
developers please tell me ... i read somany things and i am totally no where... windows was good for this
sathara said:
1. whats rooting ?
2. whats recovery for?
developers please tell me ... i read somany things and i am totally no where... windows was good for this
Click to expand...
Click to collapse
you need root for flashing custom roms that are not HTC/Google branded
you use recovery for backup your old Rom before you flash the new one ( so if brick it you can flash your old backup again )
Thats what i know
1. Rooting means get the root access right, since Linux system has very strict access control, without root access it is not possible to do any system level changes (including flashing the customized rom, change the system settings...)
2. Recovery is a special partition located in the rom, actually a recovery is a pre-built system image (a small fixed Linux system) that can be boot. With booting the recovery you can do a lot of changes to the normal booting system (ie. the /system and change the kernel with located in the boot partition in the rom). And with a lot of person's effort, the recovery image now getting easier by many preconfiged script on the menu, so that can get the system update, backup/restore and other system level changes)
rdcsueq said:
1. Rooting means get the root access right, since Linux system has very strict access control, without root access it is not possible to do any system level changes (including flashing the customized rom, change the system settings...)
2. Recovery is a special partition located in the rom, actually a recovery is a pre-built system image (a small fixed Linux system) that can be boot. With booting the recovery you can do a lot of changes to the normal booting system (ie. the /system and change the kernel with located in the boot partition in the rom). And with a lot of person's effort, the recovery image now getting easier by many preconfiged script on the menu, so that can get the system update, backup/restore and other system level changes)
Click to expand...
Click to collapse
1. That is correct.
2. That is correct.
Well done. You have passed the test. You may collect your cookie and be dismissed.
thanks bro ... i got every thing cleared and i flashed custom rom
This is insane... Creating new thread for the questions that are already answered....
Hi!
!! This is quite serious! I need to get my data (pictures, videos) out of my phone, which is possibly soft-bricked.
I did the following in hope of more usage opportunities with my new phone:
[Unlocked bootloader + Rooted it]
1. installed TWRP following this guide https://forum.xda-developers.com/p10/development/testers-twrp-t3585256;
2. rooted following this guide https://forum.xda-developers.com/p10/help/root-huawei-p10-p10-t3589946;
3. installed few apps like greenify, wi-fi hacking apps etc, and everything was good.
BUT then 1 app (don't remember which) requested that it needs SuperSU and not the one root permission app that I had. So it asked whether I want to install it. I thought - yes, why not. Then it said that before it can install SuperSU it needs to uninstall previous permission app - I clicked OK. Then it kind of started, but then failed the installation. Ok, I kind of closed it and there were no problems. But after next restart of the phone it was stuck on boot process..
I dont really care about the phone, but data on it is so important. I tried sme fast hend methrods to boot it, like wiping catch, dalvik catch, but it did not work out.
Next I looked for possobilities to rescue data, but I didn't succeed.
Easiest mentioned option - to enter twrp and connect via usb seemed promising, BUT data are shown encrypted.
Please see the picture - I tried to be as precise as I could, so that you can understand the situation.
! I can beckup all data to micro sd card, but would it decrypt after new install of stock rom (e.g. from eRecovery that Huawei provides) and allow access or not?
Please help me. I am willing to have 1-on-1 skype chat and give some donations for this as it is so important.
To mention: Rescue apps like EaseUS seems to be useless, because they state to recover data from bricked device, but then after installing soft it askes to allow usb-debbuging, but c'mon, it's not booting up.. .
So,
1. Is there a chance to recover data?
2. Is it a good sign that 16GB of data are showing even if files are shown encrypted?
3. data are also showing on pc, when connected on twrp, but also encrypted.
Any help will be appreciated!
Additionally quite important question: at this state (possible soft brick + encrypted files), is there a chance that if I make a backup to MicroSd card of all the data and then take it our to reinstall rooted stock version of my android that later puting backup in will show my files that were backuped? Could ir be so that phone luckiliy decrypt them itself because it is the same phone? Hope this is clear what I mean.
OK, hopefully all is not lost.
First things first, be REALLY careful. If you start applying factory images, wiping things and generally messing about, if you don't know what you're doing you're putting your data in a lot of danger - Huawei devices do things in weird ways, so be super sure you know the consequences of what you're doing.
Now that's out of the way... it sounds like you haven't done anything to wipe the data. Also, you've already previously unlocked the bootloader which should put you in a good situation. You need to discount TWRP as a potential solution - there is no working decryption for TWRP yet on the Kirin 960 devices and from conversations I've had, it doesn't sound like that is imminent.
What it sounds like has happened is that messing about with root has messed up something on your system partition. Which should be fixable!
As a first step, this is what I'd do.
- Check which version your phone is on if you don't know already (you should be able to find this in ' /version/special_cust/VTR-L09/hw/eu/prop/local.prop')
- Find a full dload zip for the appropriate version (use FirmwareFinder if needed)
- Download the zip an extract the dload app
- Use splitupdate to split the images out of the dload
- Boot the device to bootloader ('adb reboot bootloader' or power on with cable connected and volume down pressed) then do 'fastboot flash system SYSTEM.img'
- Flash BOOT.img too
- Try booting
Hopefully this will fix it, but at the very least it'll get your system partition back to a stock state.
Let me know how it goes. Good luck!
P
I have purchased my Samsung S10 Exynos and successfully rooted it using the only possible ways that have seems to be available so far. I have gained root, but I was wondering if anyone has solved the issue of having to turn the device on with all 3 keys held down at the same time. I understand that this is because the rooted version of the phone has be installed on the recovery of the phone, but I hope that there becomes a way to turn on the phone with root and use only the power button. I check from time to time, but it seems that this has not been solved yet. If anyone can find a solution for me so that I do not have to keep searching then I will reward them $100. An idea that I had is if there was a way to modify the power button to boot into recovery by itself? I believe this would be impossible but if anyone could think of a way to do that then that would solve the problem. I am okay with never being able to unroot the device if this would be the case.
How often do you cold boot?
reboot:
- Magisk boot menu
- adb reboot recovery
DHGE said:
How often do you cold boot?
reboot:
- Magisk boot menu
- adb reboot recovery
Click to expand...
Click to collapse
Hello, thank you for the suggestion. I thought about that idea already and I forgot to mention it in my post. I am looking for a way to do it via a cold boot. I know about the reboot into recovery method already, and I know of a way to map the power button to reboot into recovery if held down, but I am looking for a way to cold boot into recovery with just the power button.
I like your idea, but if there was a way to do it as a cold boot then that is ideally what I'm looking for. Your method would work if there was a way to just keep the phone shut down and wait until I hold the power button to turn it on and then it boot into recovery. If you can think of a way to do that then let me know.
The reason I am seeking this is because I root the S10 out to have a proprietary app on it and the app requires root to function properly. I need the power button to boot with root on the S10 so that it will always do so and my employees / customers will not access the non-rooted side of the phone by accident. The 3 button combination is too difficult, so I would need to resort so either a S8 or S9 if the S10 won't allow power button only to boot with root access. The app that I make uses a great amount of battery life so I need the ability to shut down the phone and cold boot it back into recovery. Thanks.
Hi, I assume you have rooted using the magisk-patched-recovery method (patched AP file) and if memory serves and from what I am re-reading this method does require the 3-button-combo to boot to rooted system.
When I first got my s10 and rooted this was the only method at the time, but then came custom kernels with built-in magisk.
With this method from power menu if I...
- reboot, phone will reboot to rooted system.
- power off, the power on button will boot to rooted system.
In fact I'm not sure how/if I can boot to non-rooted system with this method.
I currently on custom rom AmbasadiiRom 2.2 with AmbasadiiCruel Kernel G97xF-v3.10.
There are a few custom kernels that have built-in magisk. You will have to check rom compatibility but believe they work on samsung stock based firmware/roms, AmbasadiRomi is based on stock firmware.
- Cruel Kernel
- ThundeRStormS kernel
If you like I can provide a step-by-step, but you will lose all data as it will require flashing stock unpatched firmware, unpatched twrp in odin then custom rom (optional - depending on if the custom kernel does work on stock firmware) & custom kernel.
pjc21 said:
Hi, I assume you have rooted using the magisk-patched-recovery method (patched AP file) and if memory serves and from what I am re-reading this method does require the 3-button-combo to boot to rooted system.
When I first got my s10 and rooted this was the only method at the time, but then came custom kernels with built-in magisk.
With this method from power menu if I...
- reboot, phone will reboot to rooted system.
- power off, the power on button will boot to rooted system.
In fact I'm not sure how/if I can boot to non-rooted system with this method.
I currently on custom rom AmbasadiiRom 2.2 with AmbasadiiCruel Kernel G97xF-v3.10.
There are a few custom kernels that have built-in magisk. You will have to check rom compatibility but believe they work on samsung stock based firmware/roms, AmbasadiRomi is based on stock firmware.
- Cruel Kernel
- ThundeRStormS kernel
If you like I can provide a step-by-step, but you will lose all data as it will require flashing stock unpatched firmware, unpatched twrp in odin then custom rom (optional - depending on if the custom kernel does work on stock firmware) & custom kernel.
Click to expand...
Click to collapse
Awesome. Your solution sounds perfect for what I was looking for. Yes, I got my S10 back over a year ago and rooted it with patched AP file and magisk. I was only able to find that method even up until yesterday. I would like a step by step if you are able to quickly put one together. If it works then I am glad to grant you the reward for your help. I am willing to do this in the easiest way possible, even if it requires wiping data. I never used the phone so wiping is no problem at all. I am looking to do this to several devices so the easiest and fastest way would be the best. I will look into your comments and see if I can figure out doing this over this weekend. Will keep everyone updated.
pjc21 said:
Hi, I assume you have rooted using the magisk-patched-recovery method (patched AP file) and if memory serves and from what I am re-reading this method does require the 3-button-combo to boot to rooted system.
When I first got my s10 and rooted this was the only method at the time, but then came custom kernels with built-in magisk.
With this method from power menu if I...
- reboot, phone will reboot to rooted system.
- power off, the power on button will boot to rooted system.
In fact I'm not sure how/if I can boot to non-rooted system with this method.
I currently on custom rom AmbasadiiRom 2.2 with AmbasadiiCruel Kernel G97xF-v3.10.
There are a few custom kernels that have built-in magisk. You will have to check rom compatibility but believe they work on samsung stock based firmware/roms, AmbasadiRomi is based on stock firmware.
- Cruel Kernel
- ThundeRStormS kernel
If you like I can provide a step-by-step, but you will lose all data as it will require flashing stock unpatched firmware, unpatched twrp in odin then custom rom (optional - depending on if the custom kernel does work on stock firmware) & custom kernel.
Click to expand...
Click to collapse
I just read some info on the links you provided and i think i can figure it out. if i have any trouble then ill let you know. Dont worry about a step by step for now unless I have any trouble. Thanks!
Here is a bit of a step-by-step for Samsung s10 Exynos Model:SM-G973F
Info below is based on using December Security patch: 2020-12-01 firmware G973FXXS9DTK9 (Android 10) and Ambasadii Rom
NOTICE: The easiest and fastest way would probably be flashing kernel with stock firmware/rom. I have only done custom (but stock based) roms with kernel so am assuming the steps (5a.) for stock firmware/rom, you may want to post in chosen kernel thread to confirm if those steps are correct.
- both kernels I mentioned say they are compatibly with stock roms & AmbasadiiCruel Kernel is based on Cruel Kernel so I assume that would also work on stock rom.
This assumes you have already unlocked your bootloader, if not check this Recovery thread under Instructions: Odin (windows) - steps 1-6 for how to unlock bootloader.
1. Download all files needed to pc.
- Current latest firmware G973FXXS9DTK9, I use frija tool as downloading from samfirmware.com is very slow.
Enter Model, CSC, check the auto box & click check update and download.
Once complete unzip with 7Zip or preferred zip tool.
- In Recovery thread download latest twrp for device, is this case for S10 G973F latest twrp is - twrp-3.5.0_9-1-beyond1lte.img.tar
Under Instructions: Odin (windows) download
- Odin v3.14.1
- avb disabled vbmeta.tar
- click link to multidisabler-samsung-2.* and download latest version from there, currently multidisabler-samsung-3.1.zip
If sticking with stock and custom kernel
- easiest one looks like it would be Cruel kernel or AmbasadiiCruel kernel.
- check kernel thread of choice for compatibility with stock firmware and specific install instructions.
For custom rom in this example for Ambasadii rom
- Download files from Ambasadii rom site
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip (rom does include previous kernel 3.9 but this one is updated to latest magisk 21.2)
Bootlogo patcher - this will get rid of the warning about bootloader being unlocked when booting phone. (optional)
TWRP_Bootlogo_patcher.zip
Copy the below files to phones external SDCard
- multidisabler-samsung-3.1.zip
- TWRP_Bootlogo_patcher.zip (optional)
- chosen kernel zip - if sticking with stock
Custom Rom files
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip
2. Flashing stock firmware - Odin
- Open Odin on pc
- Turn off the phone
- Use vol down + bixby, then connect usb cable to phone from pc to start the phone in download mode, press vol up to confirm and go to download mode.
- In Odin under log you should see added, I also like to turn off auto reboot under the options tab and do manual reboot once complete but that's up to you.
- Add BL, AP, CP & CSC from the unzipped firmware downloaded in step 1. The AP & CSC can take a little time as they are larger files.
- Once all files added click start and wait until complete, you should see SUCCESS in the top left area once done.
- If you turned off auto-reboot then unplug usb and do manual reboot by pressing vol down + power for 7 seconds, else phone should reboot automatically then unplug.
3. Once phone boots up
- complete setup and connect to Wi-Fi or data
- skip adding Google & Samsung accounts.
- enable developer settings & check OEM unlock is on.
- turn off the phone.
4. Flashing TWRP Recovery - Odin
- In the Recovery thread under Instructions: Odin (windows) continue on from step 8 including formatting data and flashing multidisabler zip which you copied to SDCard.
- in twrp go back to wipe and select advanced and wipe data, cache & dalvik-cache
5a. If sticking with stock & custom kernel - Read NOTICE at top of post
Assumed Steps
- Still in twrp recovery go back to main menu
- select install and flash kernel zip, then TWRP_Bootlogo_patcher.zip
- Not sure if magisk_safetynet_fix is needed or works on stock, would need to confirm in Ambasadii thread.
- go back to main menu and select reboot & system
- give the phone a few minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
OR
5b. If flashing Custom Rom & Kernel - steps below for Ambasadii Rom
- Still in twrp recovery go back to main menu
- select install and flash ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip, choose options in aroma - once the install is complete exit back to twrp recovery
- select and flash mods_DTJA-v1.3.4.zip, then magisk_safetynet_fix.zip, then AmbasadiiCruel-G97xF-v3.10.zip, then TWRP_Bootlogo_patcher.zip
- once you have flashed all files go back to main menu and select reboot & system
- give the phone about 8 minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
6. If you went with Ambasadii Rom
- you will then notice status bar icons are pushed to the right behind the camera
- open rom control, grant superuser rights
- select status bar/options and play around with notch adjustments and positions
- can be a little confusing to start but play around and you'll get the hang of it.
Hope this info helps, let me know if you need any clarification/detail to any of the steps
Also no need for reward, happy to help
pjc21 said:
Here is a bit of a step-by-step for Samsung s10 Exynos Model:SM-G973F
Info below is based on using December Security patch: 2020-12-01 firmware G973FXXS9DTK9 (Android 10) and Ambasadii Rom
NOTICE: The easiest and fastest way would probably be flashing kernel with stock firmware/rom. I have only done custom (but stock based) roms with kernel so am assuming the steps (5a.) for stock firmware/rom, you may want to post in chosen kernel thread to confirm if those steps are correct.
- both kernels I mentioned say they are compatibly with stock roms & AmbasadiiCruel Kernel is based on Cruel Kernel so I assume that would also work on stock rom.
This assumes you have already unlocked your bootloader, if not check this Recovery thread under Instructions: Odin (windows) - steps 1-6 for how to unlock bootloader.
1. Download all files needed to pc.
- Current latest firmware G973FXXS9DTK9, I use frija tool as downloading from samfirmware.com is very slow.
Enter Model, CSC, check the auto box & click check update and download.
Once complete unzip with 7Zip or preferred zip tool.
- In Recovery thread download latest twrp for device, is this case for S10 G973F latest twrp is - twrp-3.5.0_9-1-beyond1lte.img.tar
Under Instructions: Odin (windows) download
- Odin v3.14.1
- avb disabled vbmeta.tar
- click link to multidisabler-samsung-2.* and download latest version from there, currently multidisabler-samsung-3.1.zip
If sticking with stock and custom kernel
- easiest one looks like it would be Cruel kernel or AmbasadiiCruel kernel.
- check kernel thread of choice for compatibility with stock firmware and specific install instructions.
For custom rom in this example for Ambasadii rom
- Download files from Ambasadii rom site
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip (rom does include previous kernel 3.9 but this one is updated to latest magisk 21.2)
Bootlogo patcher - this will get rid of the warning about bootloader being unlocked when booting phone. (optional)
TWRP_Bootlogo_patcher.zip
Copy the below files to phones external SDCard
- multidisabler-samsung-3.1.zip
- TWRP_Bootlogo_patcher.zip (optional)
- chosen kernel zip - if sticking with stock
Custom Rom files
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip
2. Flashing stock firmware - Odin
- Open Odin on pc
- Turn off the phone
- Use vol down + bixby, then connect usb cable to phone from pc to start the phone in download mode, press vol up to confirm and go to download mode.
- In Odin under log you should see added, I also like to turn off auto reboot under the options tab and do manual reboot once complete but that's up to you.
- Add BL, AP, CP & CSC from the unzipped firmware downloaded in step 1. The AP & CSC can take a little time as they are larger files.
- Once all files added click start and wait until complete, you should see SUCCESS in the top left area once done.
- If you turned off auto-reboot then unplug usb and do manual reboot by pressing vol down + power for 7 seconds, else phone should reboot automatically then unplug.
3. Once phone boots up
- complete setup and connect to Wi-Fi or data
- skip adding Google & Samsung accounts.
- enable developer settings & check OEM unlock is on.
- turn off the phone.
4. Flashing TWRP Recovery - Odin
- In the Recovery thread under Instructions: Odin (windows) continue on from step 8 including formatting data and flashing multidisabler zip which you copied to SDCard.
- in twrp go back to wipe and select advanced and wipe data, cache & dalvik-cache
5a. If sticking with stock & custom kernel - Read NOTICE at top of post
Assumed Steps
- Still in twrp recovery go back to main menu
- select install and flash kernel zip, then TWRP_Bootlogo_patcher.zip
- Not sure if magisk_safetynet_fix is needed or works on stock, would need to confirm in Ambasadii thread.
- go back to main menu and select reboot & system
- give the phone a few minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
OR
5b. If flashing Custom Rom & Kernel - steps below for Ambasadii Rom
- Still in twrp recovery go back to main menu
- select install and flash ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip, choose options in aroma - once the install is complete exit back to twrp recovery
- select and flash mods_DTJA-v1.3.4.zip, then magisk_safetynet_fix.zip, then AmbasadiiCruel-G97xF-v3.10.zip, then TWRP_Bootlogo_patcher.zip
- once you have flashed all files go back to main menu and select reboot & system
- give the phone about 8 minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
6. If you went with Ambasadii Rom
- you will then notice status bar icons are pushed to the right behind the camera
- open rom control, grant superuser rights
- select status bar/options and play around with notch adjustments and positions
- can be a little confusing to start but play around and you'll get the hang of it.
Hope this info helps, let me know if you need any clarification/detail to any of the steps
Also no need for reward, happy to help
Click to expand...
Click to collapse
Hey There, Been busy lately and I haven't gotten around to trying any of these methods until today. Today I attempted the stockrom+CruelKernel. I am having a strange problem. I am acquiring root but as a read-only. I can not make any changes to system files, I can only view them. Can you tell me if you are able to modify or add to the system directory? Let me know. I know your phone is running custom rom + custom kernel, so I just might have to do that if that is the only fix. I have tried several things and read all of the threads but can not find anyone else that is experiencing this issue / I can not find a fix. I'm about to try the custom rom (stock based) + custom kernel to see if that works. If you can tell me if you have access to read/write system files then let me know so I know if this is even possible. Thanks.
I have found out that I can modify system files through twrp recovery, but when I boot into the main operating system then I have root but as read-only.
Hey, sorry for late reply - ever since xda updated it's not sending me emails when I get a notification.
As for the system directory being read-only, I believe this is normal even with root. Root just gives access to the /root dir that you would not normally have without it.
- my system dir permissions by default are 755/rwxr-xr-x
After a bit of searching looks like there are a few ways to change permissions
- twrp, can mount system as r,w - but as you said this reverts on reboot
- adb shell, and chmod permissions, same why you do with linux
- in android using either root explorer or x-plore, haven't tried root explorer as it is a paid app but did test with x-plore and working fine.
check this vid on changing the root access to superuser+mount writable which allows for changes in read-only folders and how to set permissions for files/folders.
I not sure if changing permissions on the system folder itself is safe or would cause any issues, I just created a folder within system and set permissions to 644 reclusive, created some files and rebooted - created folders/files and modified permissions remained fine after reboot.
If you need write permissions in system to install apps as system/app you may find this magisk module useful, it's called App Systemizer which allows you to use apps as system apps systemlessly. Just search in magisk modules.
Hope this helps.
pjc21 said:
Hey, sorry for late reply - ever since xda updated it's not sending me emails when I get a notification.
As for the system directory being read-only, I believe this is normal even with root. Root just gives access to the /root dir that you would not normally have without it.
- my system dir permissions by default are 755/rwxr-xr-x
After a bit of searching looks like there are a few ways to change permissions
- twrp, can mount system as r,w - but as you said this reverts on reboot
- adb shell, and chmod permissions, same why you do with linux
- in android using either root explorer or x-plore, haven't tried root explorer as it is a paid app but did test with x-plore and working fine.
check this vid on changing the root access to superuser+mount writable which allows for changes in read-only folders and how to set permissions for files/folders.
I not sure if changing permissions on the system folder itself is safe or would cause any issues, I just created a folder within system and set permissions to 644 reclusive, created some files and rebooted - created folders/files and modified permissions remained fine after reboot.
If you need write permissions in system to install apps as system/app you may find this magisk module useful, it's called App Systemizer which allows you to use apps as system apps systemlessly. Just search in magisk modules.
Hope this helps.
Click to expand...
Click to collapse
Cool, I'll give your suggestions a try. I'm a fan of ES File Explorer. They have a root explorer built in their app and previously I had a S8 Exynos and a S9 Exynos and that app worked for those phones but with this S10 the switch is grayed out and no other app is working for me either. On my older S8 Exynos and S9 Exynos I rooted with stock-rom + stock-kernel and just needed TWRP+Magisk and I always was able to modify or add/delete system files with ES file explorer. I guess Samsung is getting more and more strict on allowing this by making us hop through more hoops in order to do so. So far I only have ready only system files on the S10 Exynos which is new to me because the S8 and S9 always allowed modifying system files in the past but I will try your methods you suggested. Worst case I'll attempt the custom-rom + custom-kernel and see if that works. Right now I have stock-rom+custom-kernel. I was able to make changes in the system files in TWRP but hopefully your method will allow me to edit system files without having to switch to TWRP every time I want to change something. I will keep you updated.
On a side note I just rooted a Samsung S20 Exynos and turns out that the system files are read only everywhere whether in TWRP or not, so Samsung keeps making things more difficult on us all. I currently have no way of modifying system files on the S20 no matter what I try but that phone is still much newer so I will give the magicians more time before I look into the forums more for that phone. Right now if I can get the S10 Exynos then I'll be happy.
I'll let you know how things progress. If I get what I need done with this S10 then I am happy to give you a donation for your help in this matter. I would not have gotten this far without your help. Previously the S8 and S9 days were so much easier and people had youtube videos galore that described how to root. The process was easy and everything was unlocked as read write back in the S8 and S9 days.
Yeah I use to use ES on android 6-8 then moved of to solid explorer, very similar ui to ES and also has root explorer but unfortunately it does not work to change permissions on s10 android 10 (bloody samsung/google). So far the only free one I have found is x-plore to be able to do this now. Looks like google is locking down android even more now with android 11
Would it be possible to backup different images from different GSI ROMs to be able to test and restore each one without losing all the apps, configuration, etc. in the process.
For example:
1. Install "GSI name1" configure it, install apps, my Google account, etc.
2. Somehow, make a backup of the required partitions "backup name1" (At the computer?)
3. Install "GSI name2" configure it, install apps, my Google account, etc. (Not necessarily the same apps than before).
4. Somehow make a backup of the required partitions "backup name2".
5. Continue testing other GSI or restoring one of the previous ones from the backups and be able to use the phone as it was before, including apps, configuration, etc.
I can imagine two ways to face this task:
A. Using a custom recovery to backup partitions to SD card.
B. Using fastboot or mtk_client to backup partitions to the PC.
Would be easy? Possible? Not recommendable for some reason?
I am new on this flashing-bricking-sweating-unbricking thing, so I would appreciate feedback.
Thank you!
Hi
If your goal is to test the GSIs, it's easier to use the DSU-sideloader instead of the backup.
This app enables you to dual boot.
You will be able to move back and forth between images. Even if you get into a boot loop, you can return to the original image just by rebooting.
If you have root, this app will be easier because there will be less operations.
https://github.com/VegaBobo/DSU-Sideloader
I have been taking a look to the DSU concept. It is interesting, but not what I want. Also, it requires the main ROM to be stock ROM (maybe in future is fine to use with custom ROMs).
DSU would be perfect if you want to keep romA and romB working in parallel in your daily life (for example, one for work and business and the other one for gaming and social apps).
What I want to do is to test romA for a while, move to romB for a while, if I prefer romA, reinstall it and forget about romB (literally, delete it). Maybe in few months, backup romA again and check romC for a while...
As I do not want to be swapping from one to another in daily life, it does not make sense to reserve space for having both simultaneously ready to work on the phone.
By now I have been learning about adb and recovery backup options. I need to check more during the next days, but I noticed that from Recovery, I can also use adb (it says not authorized device, but that is for not being rooted yet, I suppose). If it is possible to use adb from recovery after rooting, it would be easy to have a PC software for backing up ROMs easily (system, data and userdata partitions?).
I will keep researching about it...
The DSU does not have to be a stock rom.
It's just desirable.
Currently I have crdroid GSI as the first OS and the second OS is trying several OSs.
If you try it, you'll notice how easy it is.
Currently, TWRP does not support backup or encryption on Android 12. It is the same even if it is the official latest of other models.
I have a 128GB model, so it took too long to back up using mtkclient and I quit halfway through.
The problem is time and encryption, keep them in mind.
Currently, TWRP does not support backup or encryption on Android 12. It is the same even if it is the official latest of other models
Click to expand...
Click to collapse
Well, definitely untrue now as most devices have got it sorted out with decryption, Android 12 being a pain some devices got 13 done before 12, but as of the time you wrote this post my device Motorola stylus 22 5g Qualcomm, we hadn't figured out the decryption yet but you could definitely just patch your fstab in vendor either by hand or with DFE neo, to disable the encryption and TWRP would run fine. You would just have to make that first format reboot back to recovery immediately and while it still stays the data from a fresh format flash the other handy RO2RW re zip and DFE neo. Honestly the boot times are so much better without decryption I don't think I would go back as long as I've got a password on orange fox or whatever.
Hi guys, it's a while since my last post on XDA, but a couple of days ago I got that phone and I started playing with it.
I spent literally one day to figure out how to get the damn thing working. I NEEDED Android 10 (too long to explain why, given I usually stick with the oldest version available)
The problem is that the broken lockscreen is just the tip of the iceberg, with broken biometrics and/or keystore a lot of apps are broken as well (banking apps, billing apps, and also simpler apps that relies on such features (like the current Parallels RDP client)
Long story short, after a lot of reading here and elsewhere looks like no one before me had a fully working A6+ with root and A10, so I accepted the challenge and used a lot of my free time flashing and reflashing and testing, and finally the stubborn thing surrended.
So below is what what you need to do to to have a fixed phone
(I assume you have already unlocked your bootloader)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
#1 Flash Android 10 with odin (I suggest to use an U5 build, so you can go back to Android 9 (if you want/need to)
#2 Boot the phone once, skip the google account part but connect it to internet once or you will be stick to PRENORMAL condition (and you can't flash anything except official firmwares)
#3 Extract boot.img from the official firmware using 7zip ZETA STANDARD (not the plain 7zip!!!). C opy the file to the phone (say the download folder)
#4 Install Magisk 24 (not 25, not 22), Magisk 23 may work as well. Use magisk to install itself on the boot.img file (it's your only option since the phone isn't yet rooted), copy the patched file back to your PC, RENAME IT to boot.img, and compress it to boot.tar using 7zip
#5 Use odin, be sure to uncheck the autoreboot option then flash boot.tar, w/o rebooting the phone flash the TRWP recovery (disconnect and reconnect the USB cable before the 2nd flash operation).
Use the old twrp_3.2.3-1_sm-a605_141218.tar (it's buggy, but newer recoveries 3.5.x.x are more buggy, in a different way)
#6 reboot to recovery, format data (I mean FORMAT not just wipe !!!), then reboot to recovery (if you can mount the data partition you are OK for the next step)
#7 Install the lockscreen fix for Pie SM-A605-keymaster-fix-by-Not_Sure.zip (here)
#8 Install Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (not Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip or no-verity-opt-encrypt-6.0.zip as suggested in other threads), don't install other suggested files like "RMM-disable-something")
#9 Reboot to system, and you are almost done
#10 check the lockscreen, if everything is ok, install the magisk 24 apk, and open it (it may ask to do additional configurations and reboot the phone
#11 enjoy your rooted and fully working phone
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Optionally you can flash the latest U8 android 10 w/o having to upgrade your bootloader, to do so you can flash just the system and vendor partitions.
To do so you have to extract them from the AP file from the very latest FW for your phone then recompress the img files to tar (same thing as boot file described in #3 for boot image.
If you do so you need to repeat the above steps starting from #7
The lockscreen fix still works on freshest A10 (tested personally)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
That's all, I hope this help the (few) people who owns this phone.
The Solutor said:
Hi guys, it's a while since my last post on XDA, but a couple of days ago I got that phone and I started playing with it.
I spent literally one day to figure out how to get the damn thing working. I NEEDED Android 10 (too long to explain why, given I usually stick with the oldest version available)
The problem is that the broken lockscreen is just the tip of the iceberg, with broken biometrics and/or keystore a lot of apps are broken as well (banking apps, billing apps, and also simpler apps that relies on such features (like the current Parallels RDP client)
Long story short, after a lot of reading here and elsewhere looks like no one before me had a fully working A6+ with root and A10, so I accepted the challenge and used a lot of my free time flashing and reflashing and testing, and finally the stubborn thing surrended.
So below is what what you need to do to to have a fixed phone
(I assume you have already unlocked your bootloader)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
#1 Flash Android 10 with odin (I suggest to use an U5 build, so you can go back to Android 9 (if you want/need to)
#2 Boot the phone once, skip the google account part but connect it to internet once or you will be stick to PRENORMAL condition (and you can't flash anything except official firmwares)
#3 Extract boot.img from the official firmware using 7zip ZETA STANDARD (not the plain 7zip!!!). C opy the file to the phone (say the download folder)
#4 Install Magisk 24 (not 25, not 22), Magisk 23 may work as well. Use magisk to install itself on the boot.img file (it's your only option since the phone isn't yet rooted), copy the patched file back to your PC, RENAME IT to boot.img, and compress it to boot.tar using 7zip
#5 Use odin, be sure to uncheck the autoreboot option then flash boot.tar, w/o rebooting the phone flash the TRWP recovery (disconnect and reconnect the USB cable before the 2nd flash operation).
Use the old twrp_3.2.3-1_sm-a605_141218.tar (it's buggy, but newer recoveries 3.5.x.x are more buggy, in a different way)
#6 reboot to recovery, format data (I mean FORMAT not just wipe !!!), then reboot to recovery (if you can mount the data partition you are OK for the next step)
#7 Install the lockscreen fix for Pie SM-A605-keymaster-fix-by-Not_Sure.zip (here)
#8 Install Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (not Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip or no-verity-opt-encrypt-6.0.zip as suggested in other threads), don't install other suggested files like "RMM-disable-something")
#9 Reboot to system, and you are almost done
#10 check the lockscreen, if everything is ok, install the magisk 24 apk, and open it (it may ask to do additional configurations and reboot the phone
#11 enjoy your rooted and fully working phone
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Optionally you can flash the latest U8 android 10 w/o having to upgrade your bootloader, to do so you can flash just the system and vendor partitions.
To do so you have to extract them from the AP file from the very latest FW for your phone then recompress the img files to tar (same thing as boot file described in #3 for boot image.
If you do so you need to repeat the above steps starting from #7
The lockscreen fix still works on freshest A10 (tested personally)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
That's all, I hope this help the (few) people who owns this phone.
Click to expand...
Click to collapse
You are amazing.... you did it MASTER.
IEarlyer i also tryed but I gived up.... when I made root I allways lost the encryption the keystore no screenlock etc ... that was unusable.
Another time I was able install working recovery but the system crashed allways. But now its perfect.
The only beauty flaw is the lack of custom roms for a6plus but now I can customize for myself.
Many respect.
Thanks for your kind words
respect and appreciation to you.
You are a true moddfanatic.
Its not about how to keep in use the old phones. Its a passion .
Im the same just lwith mouch less expertion.
Simce You solved this problem I quickly founf the next.
Thr Last 2 -3 ays II spend with a experiment to to open Sansung native callrecder. I tried mouch ways...
all Csc changers
Secret codes
and dparrser mode
wtth activity hacks
with disrcibe files edit
With an apps replacing from customrom.
Wasnnot good .Tomorrow I flash with Odin csc f
So thats what I told ya.
Really I never use this feature !!!!!!
But I can let away I WANT to solve
If a problem prevents you from doing what you imagined, it is unacceptable to us.
caiuse Its about our force in this doddned )mazrix
Will it work in Samsung a605GN?
And what do you mean by 7zip zeta standard?
JulioM18 said:
Will it work in Samsung a605GN?
And what do you mean by 7zip zeta standard?
Click to expand...
Click to collapse
This: https://github.com/mcmilk/7-Zip-zstd/releases
It is a moded version of 7zip with support for Zstandard. You need this to extract the boot.img from the firmware files.
Hope it helps
It works on Samsung A605GN. I just tested IT. Thanks!
The Solutor said:
Hi guys, it's a while since my last post on XDA, but a couple of days ago I got that phone and I started playing with it.
I spent literally one day to figure out how to get the damn thing working. I NEEDED Android 10 (too long to explain why, given I usually stick with the oldest version available)
The problem is that the broken lockscreen is just the tip of the iceberg, with broken biometrics and/or keystore a lot of apps are broken as well (banking apps, billing apps, and also simpler apps that relies on such features (like the current Parallels RDP client)
Long story short, after a lot of reading here and elsewhere looks like no one before me had a fully working A6+ with root and A10, so I accepted the challenge and used a lot of my free time flashing and reflashing and testing, and finally the stubborn thing surrended.
So below is what what you need to do to to have a fixed phone
(I assume you have already unlocked your bootloader)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
#1 Flash Android 10 with odin (I suggest to use an U5 build, so you can go back to Android 9 (if you want/need to)
#2 Boot the phone once, skip the google account part but connect it to internet once or you will be stick to PRENORMAL condition (and you can't flash anything except official firmwares)
#3 Extract boot.img from the official firmware using 7zip ZETA STANDARD (not the plain 7zip!!!). C opy the file to the phone (say the download folder)
#4 Install Magisk 24 (not 25, not 22), Magisk 23 may work as well. Use magisk to install itself on the boot.img file (it's your only option since the phone isn't yet rooted), copy the patched file back to your PC, RENAME IT to boot.img, and compress it to boot.tar using 7zip
#5 Use odin, be sure to uncheck the autoreboot option then flash boot.tar, w/o rebooting the phone flash the TRWP recovery (disconnect and reconnect the USB cable before the 2nd flash operation).
Use the old twrp_3.2.3-1_sm-a605_141218.tar (it's buggy, but newer recoveries 3.5.x.x are more buggy, in a different way)
#6 reboot to recovery, format data (I mean FORMAT not just wipe !!!), then reboot to recovery (if you can mount the data partition you are OK for the next step)
#7 Install the lockscreen fix for Pie SM-A605-keymaster-fix-by-Not_Sure.zip (here)
#8 Install Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (not Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip or no-verity-opt-encrypt-6.0.zip as suggested in other threads), don't install other suggested files like "RMM-disable-something")
#9 Reboot to system, and you are almost done
#10 check the lockscreen, if everything is ok, install the magisk 24 apk, and open it (it may ask to do additional configurations and reboot the phone
#11 enjoy your rooted and fully working phone
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Optionally you can flash the latest U8 android 10 w/o having to upgrade your bootloader, to do so you can flash just the system and vendor partitions.
To do so you have to extract them from the AP file from the very latest FW for your phone then recompress the img files to tar (same thing as boot file described in #3 for boot image.
If you do so you need to repeat the above steps starting from #7
The lockscreen fix still works on freshest A10 (tested personally)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
That's all, I hope this help the (few) people who owns this phone.
Click to expand...
Click to collapse
It's been so long since this forum was published, and recently I came across it, purely by chance, since I gave up trying to root my A6+ (A605GN). I tried endless tutorials and invested many hours of my time and rest, and here is my reward.
I am totally grateful for giving you the time to explain these steps in detail, and help the community that has this device (still) and can configure it to their liking.
A big hug and blessings. You have saved my life. <3