Related
ZTE_A2017_V1.1.0B15_BootStack_Fix_by_djkuz.zip (includes patches fixing issues with EDL, FASTBOOT and ROOT)
CRC32: 797405C0
MD5: 3AFD84C314960DE0DFFAAB950A435745
SHA-1: F4C358F8CD5E043FE897E7D51FE93780C395CE42 https://4pda.ru/pages/go/?u=https%3A%2F%2Fmega.nz%2F%23!FtI3iSSa!4guZpoM2oCmgoxTiBBFA_Rt1wY1cdZTbA7WcugkLSic&e=60952279
ZTE_A2017_V1.1.0B15_StockSystem_by_djkuz.zip https://4pda.ru/pages/go/?u=https%3A%2F%2Fmega.nz%2F%23!Jp5mna5a!sS9Ns_WlvqeKRcXGjrDST43PQ09Zgb_hgIqN-5heIWg&e=60952279
CRC32: F6CD7F71
MD5: C1A3719F641ED63EE5D53E968DE6D798
SHA-1: E6E0E175663B78AC238BD1D9C620DF0FCF27E267
Instructions:
1. Go to TWRP
2. Advanced wipe - Dalvik,System,Data,Cache
3. Installing this file first : BootStack ZTE_A2017_V1.1.0B15_BootStack_Fix_by_djkuz.zip
4. This one second : StockSystem ZTE_A2017_V1.1.0B15_StockSystem_by_djkuz.zip
5. Flashing this one as well: no-verity-opt-encrypt-5.1.zip
6. wipe cache/dalvik
7. In TWRP input this command: reboot disemmcwp
8. Boot into the system
9. Check if its possible to enter edl mode (fix is already included in bootstack) Volume down + power button
10. Check you you are able to get to FASTBOOT via the combination of buttons Volumeup+Powerbutton
11. Install GApps ZTE Axon 7
Installing SuperSU:
1. Go back to recovery TWRP
2. Flash SuperSU 2.79
3. Wipe cache/dalvik
4. In the Terminal of TWRP input this command: reboot disemmcwp
5. Boot to the system and see if SuperSU is working.
Disclaimer (READ!) :
This is being updated by the amazing djkuz which is active in 4pda and sometimes here as well.
it seems that 4pda is more active then xda for apperant reasons , axon is more popular in russia.
All of this is not on my responsibility if you **** your device, your problem ( Ive just merely copied the guide from a russian forum 4pda).
Ive done this myself but I can't make root stick. (will be happy for an advice and some brainstorming on this one)
@djkuz
Can you please assist -
The root doesn't stick I follow step by step, when I enter the supersu app it says there is no root.
booth files 2.7GB? bootstak shood me smaller
yosef019 said:
booth files 2.7GB? bootstak shood me smaller
Click to expand...
Click to collapse
Fixed
parazite69 said:
@djkuz
Can you please assist -
The root doesn't stick I follow step by step, when I enter the supersu app it says there is no root.
Click to expand...
Click to collapse
Very strange, what version of SuperSu was used? 2.79 stable only works correctly.
djkuz said:
Very strange, what version of SuperSu was used? 2.79 stable only works correctly.
Click to expand...
Click to collapse
Yes, just as the one I have posted here. Followed exactly as it says in your guide.
Hi guys. Been following the thread in 4pda too. Could you please post a mirror for te edl_fix.zip here? I can't download it in 4pda as i can't create an account there. Thanks so much.
parazite69 said:
Yes, just as the one, I have posted here. Followed exactly as it says in your guide.
Click to expand...
Click to collapse
Try this:
1. Go back to recovery TWRP
2. Flash patching boot (in boot partition) https://mega.nz/#!dhwCHLqI!3lmYs2wV6DGYwqteU_h98ffZbeJp9lVXCyQzz-wQG3A (not need to flash no-verity-opt-encrypt-5.1.zip)
2. Flash SuperSU 2.79 https://mega.nz/#!J8BggKDS!OYSLIQ4vSntRGO8lBWnp8frBymtfC_oo57bzIGubf2A
3. Wipe cache/dalvik
4. In the Terminal of TWRP input this command: reboot disemmcwp !!!!!!!!!!!!
---------- Post added at 11:14 PM ---------- Previous post was at 11:11 PM ----------
otaconremo said:
Hi guys. Been following the thread in 4pda too. Could you please post a mirror for te edl_fix.zip here? I can't download it in 4pda as i can't create an account there. Thanks so much.
Click to expand...
Click to collapse
https://mega.nz/#!VhJDjAQZ!CDbx4YW_LIVQedY_7RixQk-7J6Q0T--W8lYhIVSP0-Q
djkuz said:
Try this:
1. Go back to recovery TWRP
2. Flash patching boot (in boot partition) https://mega.nz/#!dhwCHLqI!3lmYs2wV6DGYwqteU_h98ffZbeJp9lVXCyQzz-wQG3A (not need to flash no-verity-opt-encrypt-5.1.zip)
2. Flash SuperSU 2.79 https://mega.nz/#!J8BggKDS!OYSLIQ4vSntRGO8lBWnp8frBymtfC_oo57bzIGubf2A
3. Wipe cache/dalvik
4. In the Terminal of TWRP input this command: reboot disemmcwp !!!!!!!!!!!!
---------- Post added at 11:14 PM ---------- Previous post was at 11:11 PM ----------
https://mega.nz/#!VhJDjAQZ!CDbx4YW_LIVQedY_7RixQk-7J6Q0T--W8lYhIVSP0-Q
Click to expand...
Click to collapse
Amazing worked like charm!!! Thank you.
If you may share a bit on what was wrong ?
update :
It still says its not rooted
Thank you so much @djkuz.
@djkuz
I have moved straight from Zad 0.3mix with Chinese
Bootstack to your guide followed exactly and then implemented the fix you suggested here .
Still the SuperSU says its unrooted, but it constantly grants permission to titanium backup... But still TB doesn't work.
Thank you for assisting on this.
parazite69 said:
@djkuz
I have moved straight from Zad 0.3mix with Chinese
Bootstack to your guide followed exactly and then implemented the fix you suggested here .
Still the SuperSU says its unrooted, but it constantly grants permission to titanium backup... But still TB doesn't work.
Thank you for assisting on this.
Click to expand...
Click to collapse
Have you tried issuing command "reboot disemmcwp" in twrp after installing supersu?
otaconremo said:
Have you tried issuing command "reboot disemmcwp" in twrp after installing supersu?
Click to expand...
Click to collapse
Yes :crying:
parazite69 said:
@djkuz
I have moved straight from Zad 0.3mix with Chinese
Bootstack to your guide followed exactly and then implemented the fix you suggested here .
Still the SuperSU says its unrooted, but it constantly grants permission to titanium backup... But still TB doesn't work.
Thank you for assisting on this.
Click to expand...
Click to collapse
Yes, this problem occurs on some phones...
Did you flash ZTE_A2017_V1.1.0B15_BootStack_Fix_by_djkuz.zip ???
Try in TWRP:
1. Tap Mount and Check "Mount, System as Read-only"
2. Tap WIPE > ADVANCE WIPE > Select Data > Repair or Change File System and Select ext4 (All data will be deleted)
2. Tap WIPE > ADVANCE WIPE > Select Dalvik,System,Data,Cache and Swipe
3. Flash BootStack ZTE_A2017_V1.1.0B15_BootStack_Fix_by_djkuz.zip
4. Flash StockSystem ZTE_A2017_V1.1.0B15_StockSystem_by_djkuz.zip
5. Flash no-verity-opt-encrypt-5.1.zip
6. Flash SuperSU 2.79
7. wipe cache/dalvik
8. Tap ADVANCED > TERMINAL > input this command: reboot disemmcwp
djkuz said:
Yes, this problem occurs on some phones...
Did you flash ZTE_A2017_V1.1.0B15_BootStack_Fix_by_djkuz.zip ???
Try in TWRP:
1. Tap Mount and Check "Mount, System as Read-only"
2. Tap WIPE > ADVANCE WIPE > Select Data > Repair or Change File System and Select ext4 (All data will be deleted)
2. Tap WIPE > ADVANCE WIPE > Select Dalvik,System,Data,Cache and Swipe
3. Flash BootStack ZTE_A2017_V1.1.0B15_BootStack_Fix_by_djkuz.zip
4. Flash StockSystem ZTE_A2017_V1.1.0B15_StockSystem_by_djkuz.zip
5. Flash no-verity-opt-encrypt-5.1.zip
6. Flash SuperSU 2.79
7. wipe cache/dalvik
8. Tap ADVANCED > TERMINAL > input this command: reboot disemmcwp
Click to expand...
Click to collapse
Yes Ive flashed ZTE_A2017_V1.1.0B15_BootStack_Fix_by_djkuz.zip .
I will try it later today and update on the outcome.
Appreciate the help.
parazite69 said:
Yes Ive flashed ZTE_A2017_V1.1.0B15_BootStack_Fix_by_djkuz.zip .
I will try it later today and update on the outcome.
Appreciate the help.
Click to expand...
Click to collapse
And do not forget to go into the Mi-Aassistant and allow autorun SuperSU
hey is it possble return to the B13 6.0 china phone install TWRP and then install this
my pc cant recodnize the phone in EDL mode (with drivers installed)
yosef019 said:
hey is it possble return to the B13 6.0 china phone install TWRP and then install this
my pc cant recodnize the phone in EDL mode (with drivers installed)
Click to expand...
Click to collapse
Yes, it is possible, but the lack of the ability to flash through the EDL is very dangerous !!!
Try:
1. Install the driver from the phone, selecting in settings - connection to the PC - installing the drivers!
2. Boot into the EDL through the command - adb reboot edl
3. Try using another version of MyFlash (for example Beta) and use another USB port on your computer.
And if Windows determines phone as Qualcomm HS-USB QDLoader 9008, but Miflash can not see it - reboot the phone in EDL again!
Don't forget to change the speed of the com port (Qualcomm HS-USB QDLoader 9008) to 115200 (instead of 9600)
djkuz said:
And do not forget to go into the Mi-Aassistant and allow autorun SuperSU
Click to expand...
Click to collapse
Worked!
Thankyou
Android "P" is the upcoming ninth major version of the Android operating system. It was first announced by Google on March 7, 2018, and the first developer preview was released on the same day. The second developer preview is expected to be released at the next Google I/O developer conference.
Requirements :
Qcom fully treblized device with 8.1 vendor
Global Bugs :
VoLTE
Device specific Bugs :
Mi5 = Reboot Loop into TWRP (Fixed by restore files)
ANDROID P DP3
installation :
- Flash [JDCTeam][TREBLE][v4][Gemini] The Full Treble support project HERE
- Unzip and Flash P-DP3-sGSI.img HERE
- Flash POST-sGSI_1_v0.9.zip HERE
- Flash POST-sGSI_2_v0.12.zip HERE
- Flash POST-sGSI_3.zip HERE
- Flash P-lag-fix.zip file below thread
- Flash incall2.zip HERE
- Reboot
When flashing POST-sGSI untill incall shown error in twrp, Go back to TWRP Home > Mount > check vendor and system
After bootup, you need to install Google Play services 12.8.72 (100400-202717283) HERE
If you are facing with bug Reboot Loop(always reboot into TWRP) you need to restore this backup file from me.
Unzip and put that folder at TWRP/Backups
Goto TWRP > Restore > Check system and vendor only > Reboot.
SECOND METHOD : Restore before 1st boot.
- Flash [JDCTeam][TREBLE][v4][Gemini] The Full Treble support project HERE
- Unzip and Flash P-DP3-sGSI.img HERE
- Flash POST-sGSI_1_v0.9.zip HERE
- Flash POST-sGSI_2_v0.12.zip HERE
- Flash POST-sGSI_3.zip HERE
- Restore this backup file
(Make sure choose System and Vendor only, Dont choose boot, system image, or vendor image and the size is 2101MB).
- Flash P-lag-fix.zip file below thread
- Flash incall2.zip HERE
- Reboot (If stuck at google logo about 3-5mins, try to force shutdown your phone, and turn it on again... it should be work.)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
ANDROID P DP4
CLEAN FLASH IS HIGHLY RECOMMEND
- Flash [JDCTeam][TREBLE][v4][Gemini] The Full Treble support project HERE
- Unzip and Flash P-DP4-sGSI-Aonly.zip HERE
- Flash POST-sGSI_1_v0.11.zip HERE
- Flash POST-sGSI_2_v0.14.zip HERE
- Flash POST-sGSI_3.zip HERE
- Restore this backup file
(Make sure choose System and Vendor only, Dont choose boot, system image, or vendor image and the size is 2180MB).
- Incall.zip already included. Dont need to flash it.
- Flash p-lag-fix DP4.zip file below thread
- Reboot
If your device become reboot loop into TWRP, like in DP3
- Restore this backup file
(Make sure choose System and Vendor only, Dont choose boot, system image, or vendor image and the size is 2180MB).
Click to expand...
Click to collapse
ANDROID P DP5
CLEAN FLASH IS HIGHLY RECOMMEND
- Flash [JDCTeam][TREBLE][v4][Gemini] The Full Treble support project HERE
- Unzip and Flash P-DP5-sGSI-Aonly.zip HERE
- Flash POST-sGSI_1_v0.13.zip HERE
- Flash POST-sGSI_2_v0.16.zip HERE
- Flash POST-sGSI_3 v0.2.zip HERE
- Flash lag-fix-DP5 attached below.
- Mount Vendor on TWRP
- Go to TWRP Advanced->Terminal, type the following and press enter
echo persist.sys.disable_rescue=true >> /vendor/build.prop
- Reboot to System
IF YOU STILL REBOOT INTO RECOVERY AFTER 1ST BOOT.
after flash POST-sGSI_3 v0.2.zip
- Restore this backup file
(Make sure choose System and Vendor only, Dont choose boot, system image, or vendor image and the size is 2180MB).
- Incall.zip already included. Dont need to flash it.
- Flash lag-fix-DP5 attached below.
- Reboot
Click to expand...
Click to collapse
Android P Public Release 1 (PR1)
1. Flash JDCTeam Full Treble Support Project
2. UNZIP and flash Pie A-only as System Image.
3. Mount System and Vendor on TWRP
4. Flash POST-sGSI_1_v0.14.zip
5. Flash POST-sGSI_2_v0.17.zip
6. Flash POST-sGSI_3_v0.2.zip
7. Mount System and Vendor on TWRP
8. Flash p-lag-fix.zip (Attached Below)
9. Mount Vendor on TWRP
10. Go to TWRP Advanced - Terminal, type the following and press enter
echo persist.sys.disable_rescue=true >> /vendor/build.prop
11. Reboot to System
12. Install Google Play Services Apk, reboot and proceed normally.
Click to expand...
Click to collapse
REBOOT LOOP THIRD METHOD by mlira1 and Maixf
1. Flash JDCTeam Full Treble Support Project
2. Flashi DP3/DP4 System Image
3. Mount System and Vendor on TWRP
4. Flash POST-sGSI_1
5. Flash POST-sGSI_2
6. Flash POST-sGSI_3 (skip if going to flash custom kernel)
7. (only if going to flash custom kernel) Flash fix.zip (attached below)
8. (optional) Flash custom kernel
9. (optional) Flash Magisk
10. Mount System and Vendor on TWRP
11. (only if flashed custom kernel) Flash POST-sGSI_3
12. Flash p-lag-fix DP3/4/5.zip
13. Mount Vendor on TWRP
14. Go to TWRP Advanced->Terminal, type the following and press enter
echo persist.sys.disable_rescue=true >> /vendor/build.prop
15. Reboot to System
16. Install Google Play Services Apk, reboot and proceed normally
Click to expand...
Click to collapse
TIPS
Mi5 'Fingerprint Always On' On Android P (Unlock when screen off, and without press any button. Just touch it FP)
- Root your Mi5 with 16.4/16.6 Treble version
- Install Karnel Auditor
- Go to Tab, Select Custom Control
- Press "+", and import this .json file
- Press 3 dots at there, check 'on boot'
- Reboot
Click to expand...
Click to collapse
Mi5 Fingerprint as Home by rmrbpt
- Root your Mi5 with 16.4/16.6 Treble version
- Install Karnel Auditor
- Go to Tab, Select Custom Control
- Press "+", and import this .json file
- Press 3 dots at there, check 'on boot'
- Reboot
Click to expand...
Click to collapse
Mi5 Double Tap to Wakeup Android P
- Root your mi5 with 16.4/16.6 Treble version
- Open Karnel Auditor
- Go to Tab
- Find 'Wake'
- Turn it on, and apply on boot
- Reboot
Click to expand...
Click to collapse
Disable backlight button
Flash Disable Backlight.zip from Magisk !
Attached below.
Click to expand...
Click to collapse
Fix Battery Drain Issue
Still working on it
Alternative for it
- Dissable Dev Mode in Setting
or
- Try custom karnel
Click to expand...
Click to collapse
Get Blue accent / Pixel theme
Add this to your /vendor/build.prop, save and reboot:
Code:
ro.boot.vendor.overlay.theme=com.google.android.theme.pixel
Click to expand...
Click to collapse
MTP Not Detected
- Goto Setting
- System > Advanced > Dev Options > Choose File Transfer at USB Default Configuration
Click to expand...
Click to collapse
How to flash custom kernel on P GSI
FLASHING CUSTOM KARNEL CAUSING YOU CANNOT ENABLE MTP FORVER AND CHARGING FROM PC/LAPTOP
- Follow instruction from flashing JDC untill POST GSI 2, dont flash POST GSI 3.
- Flash Custom Karnel
- Reboot
- Clean Flash is the only way to fix it for now
Click to expand...
Click to collapse
Fix/Solution Arnova/BSG/other dev Gcam lag when changging between front and back camera on P
- Flash Camera Switch Lag Fix.zip, attached below.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Terribly sorry but at what point did you make that "backup file"? I couldn't fix bootloop without your backup. Just wondering, since it's so large and probably mi5-only maybe you could just give us instructions how to make a working system without using someone else's backup?
After restore, have been stuck in G logo for 25 minutes, just followed the instruction
mansonstein said:
After restore, have been stuck in G logo for 25 minutes, just followed the instruction
Click to expand...
Click to collapse
Try select system only. goodluck.
mansonstein said:
After restore, have been stuck in G logo for 25 minutes, just followed the instruction
Click to expand...
Click to collapse
dont choose system image and vendor image.
but system and vendor only
bukandenny said:
dont choose system image and vendor image.
but system and vendor only
Click to expand...
Click to collapse
Yes, exactly, and I tried just system and just vendor, all stucked in G logo. Someway else to try? What causes reboot loop? Thx
If anyone successed, please let me know how you did it.
mansonstein said:
If anyone successed, please let me know how you did it.
Click to expand...
Click to collapse
3 times i used that way, and always work.
asking someone to do that, its work.
mansonstein said:
If anyone successed, please let me know how you did it.
Click to expand...
Click to collapse
try second methode above.
https://drive.google.com/open?id=1VryExVHI-14NfgIcBPp2dFiN-rzhOeNO
I've tried both the methods , but I always end up at this error, please help.
It asks for password and then just reboots into recovery.
There's also a pop up stating "There's internal problem, please contact manufacturer for details"
The above link has the images of the issue.
It would be really helpful if someone can help me boot this rom up. Thank you.
Santosh Kolur said:
https://drive.google.com/open?id=1VryExVHI-14NfgIcBPp2dFiN-rzhOeNO
I've tried both the methods , but I always end up at this error, please help.
It asks for password and then just reboots into recovery.
There's also a pop up stating "There's internal problem, please contact manufacturer for details"
Click to expand...
Click to collapse
Start from beginning.
you need to FORMAT DATA (not wipe data)
then start from beginning dude.
Santosh Kolur said:
https://drive.google.com/open?id=1VryExVHI-14NfgIcBPp2dFiN-rzhOeNO
I've tried both the methods , but I always end up at this error, please help.
It asks for password and then just reboots into recovery.
There's also a pop up stating "There's internal problem, please contact manufacturer for details"
The above link has the images of the issue.
It would be really helpful if someone can help me boot this rom up. Thank you.
Click to expand...
Click to collapse
http://xiaomitips.com/media/2016/07/Format-Data-TWRP.png
bukandenny said:
http://xiaomitips.com/media/2016/07/Format-Data-TWRP.png
Click to expand...
Click to collapse
Thank you. I got it to boot using your solution.
Santosh Kolur said:
Thank you. I got it to boot using your solution.
Click to expand...
Click to collapse
Decrypting internal storage fixes reboots?
Yes it did for me.
First method did it for me, too. I had the bootloop after first reboot and it did the trick, everything is working fine, a bit laggy, but Android P is running smooth on my phone!! I think that's very importat that after first boot you install Play Services as stated in OP and let Google finish its whole Pixel Configuration and updates, then you can try and reboot the phone, if you're hit by the bug, just follow what's in OP.
Few things if you install the GSI and have these issues:
- for Magisk, install version 16.4, just install that after you have set up the phone and stuff, you reboot to twrp and flash it, that's the way it works for me;
- if you have missing network on SIM, just go and configure your apn manually, it'll do the trick;
- for MTP, it's not working for me out of the box, the trick is to enable developers options, go to "Default USB Configuration" or something similar (I have it on italian, so I think that's how it's in English) and select the first one option;
Edit: also there's fingerprint that cannot wake the device, I've read in Telegram groups that some fixes are around for fingerprint, I'll check it out later and report if I find something interesting.
I've suceeded but my FP isn't working, already sent the logcat to the main xda page of GSI
g33k0 b3lk0w said:
I've suceeded but my FP isn't working, already sent the logcat to the main xda page of GSI
Click to expand...
Click to collapse
Cool! So I think there's no solution to this issue at the moment?
aittamattia said:
Cool! So I think there's no solution to this issue at the moment?
Click to expand...
Click to collapse
wait ill upload, u can see my chat on group
TWRP is an open source, community project. A custom recovery is used for installing custom software on your device. This TWRP has included Magisk. After a long wait, Finally, A50s can be rooted without bootloop issue using Kernel Mod. Kernel Mod based on Quantum Kernel v.1.1, edited by halcyon441 to make it works on A50s for fixing bootloop.
Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Installing TWRP and Rooting may void warranty. We are here just try to help you, don't be stupid and don't blame us if you make mistake
Downloads
TWRP_3.4.0.0_A50s_Magisk.tar
QuantumKernelv1.50_A50sxx.zip
Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Copy these 2 files to micro SD Card ( Quantumkernel and disable dm_verity )
Install TWRP and Rooting instructions:
1. Make sure the bootloader is unlocked, OEM unlock option is grey out
2. Enter Download Mod
3. Open ODIN, IMPORTANT!: Uncheck “Auto Reboot” in Options!
4. Flashing TWRP_3.4.0.0_A50s_Magisk.tar as AP in ODIN ( uncheck "Auto Reboot" )
5. Enter TWRP Recovery for first time: Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key until TWRP Recovery Mode Appears.
6. Install QuantumKernelv1.50_A50sxx.zip
8. Select Wipe -> Format data.
9. Install Disable_Dm-Verity_ForceEncrypt_01.14.2020.zip
10. Select Reboot to Recovery
11. Install Magisk Manager
12. Done!
For detail instructions WATCH THIS VIDEO
Contributors
halcyon441 and redymedan
Source Code TWRP : https://github.com/halcyon441-png/twrp_samsung_a50sxx
Source Code Kernel: https://github.com/halcyon441-png/android_samsung_exynos9610/releases/tag/v1.5
Created 2020-06-08
Updated 2020-07-23
First ?
great thanks mate, @redymedan & @halcyon441
After rooting, phone restart unroot again,, how to fix?
rockadz9 said:
After rooting, phone restart unroot again,, how to fix?
Click to expand...
Click to collapse
enter TWRP recovery then select Reboot to Recovery, each time you restart the phone normally, it will unroot it.
You can join to telegram group https://t.me/androidhowto2020
̶h̶e̶y̶ ̶@redymedan,̶ ̶d̶i̶d̶ ̶y̶o̶u̶ ̶c̶h̶e̶c̶k̶ ̶t̶h̶e̶ ̶c̶a̶m̶e̶r̶a̶?̶
̶i̶s̶ ̶i̶t̶ ̶w̶o̶r̶k̶i̶n̶g̶ ̶o̶r̶ ̶n̶o̶t̶?̶ ̶b̶e̶c̶a̶u̶s̶e̶ ̶m̶y̶ ̶c̶a̶m̶e̶r̶a̶ ̶i̶s̶n̶'̶t̶ ̶w̶o̶r̶k̶i̶n̶g̶ ̶a̶f̶t̶e̶r̶ ̶i̶ ̶f̶l̶a̶s̶h̶ ̶t̶h̶a̶t̶ ̶k̶e̶r̶n̶e̶l̶
[Edit]
My bad, turns out i was flashing the zip from A50, not the edited custom kernel from @redymedan gdrive
change to source code link to this please.
halcyon441 said:
change to source code link to this please.
Click to expand...
Click to collapse
Done!
Any chance for permanent root which persist after reboot?
Mikolaj.Q said:
Any chance for permanent root which persist after reboot?
Click to expand...
Click to collapse
You can try Smali Patcher and thick/select only "recovery reboot".
Did this working with SM-A5070
ba_alwy said:
Did this working with SM-A5070
Click to expand...
Click to collapse
not tested
Can I flash the the tar file without the magisk suffix and flash the latest magisk zip file?
If not, how can I make root persist after reboot with smalli patcher?
I tested and not working with A5070
The only thing it's root with magisk and the phone keep reset
Hi, tried doing this on my SM-A507FN/DS, couldnt flash TWRP, it said only official binaries can be flashed in download mode. Any solution @redymedan ?
muhsin_Sultan said:
Hi, tried doing this on my SM-A507FN/DS, couldnt flash TWRP, it said only official binaries can be flashed in download mode. Any solution @redymedan ?
Click to expand...
Click to collapse
You must unlock the bootloader, you get the error message because the bootloader are locked.
Watch this video how to unlock it Unlock Bootloader https://youtu.be/8j6WkOOA3f4
redymedan said:
You must unlock the bootloader, you get the error message because the bootloader are locked.
Watch this video how to unlock it Unlock Bootloader https://youtu.be/8j6WkOOA3f4
Click to expand...
Click to collapse
I already unlocked the bootloader. If you do it from a locked bootloader it would say not allowed due to oem lock. But I already unlocked it. I saw another thread where say to flash the AP file with Magisk then flash everything in odin except replace AP with the magisk patched one. Will that work @redymedan
Update TWRP 3.4.0.0 and Quantum Kernel v1.50
Thanks to halcyon441 for the Good Jobs :good:
sm-5070
hello,
I tested with a A50s SM-5070. TWRP is well flashed, but the phone doesn't want to reboot in recovery.
Then i flashed the stock ROM
On which version of A50s is it tested ?
Sony's bootloader unlock page added the xperia 10 II to the list.
It's wrongly listed as "Xperia X10 II", so it's near the middle of the list, but gives the code with the IMEI
Edit:
Can't post link yet, the unlock page is: https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
I've done it but i'm facing a problem with rooting could you help me with that ?
hq8aus said:
I've done it but i'm facing a problem with rooting could you help me with that ?
Click to expand...
Click to collapse
As long as BL is unlocked, you may be able to root your device using XperiFirm, UnSIN and Magisk.
- XperiFirm > Download fw
- UnSIN > Get the boot_XXXX.sin file from the downloaded fw folder, and drop it over unsin.exe (you'll get boot_XXXX.img file).
- Move the boot_XXXX.img file to the device's internal storage (or sdcard).
- Install Magisk Manager app
- Magisk Manager app > Install > Uncheck 'Keep AVB 2.0/dm-verity' > Next > Select and patch a file > Choose the boot_XXXX.img (you'll get /Download/magisk_patched.img)
- Flash magisk_patched.img with fastboot with command:
Code:
fastboot flash boot magisk_patched.img
- Reboot
If something goes wrong, you'll need to flash original stock boot img file (boot_XXXX.img) with fastboot (or even flash whole fw again).
Try it at your own risk.
serajr said:
As long as BL is unlocked, you may be able to root your device using XperiFirm, UnSIN and Magisk.
- XperiFirm > Download fw
- UnSIN > Get the boot_XXXX.sin file from the downloaded fw folder, and drop it over unsin.exe (you'll get boot_XXXX.img file).
- Move the boot_XXXX.img file to the device's internal storage (or sdcard).
- Install Magisk Manager app
- Magisk Manager app > Install > Uncheck 'Keep AVB 2.0/dm-verity' > Next > Select and patch a file > Choose the boot_XXXX.img (you'll get /Download/magisk_patched.img)
- Flash magisk_patched.img with fastboot with command:
Code:
fastboot flash boot magisk_patched.img
- Reboot
If something goes wrong, you'll need to flash original stock boot img file (boot_XXXX.img) with fastboot (or even flash whole fw again).
Try it at your own risk.
Click to expand...
Click to collapse
Thank you for the tutorial i will try it after few hour
I have one question : my phone refuse to enter recovery mode once the recovery mode boot the phone restart and start normally so i'm surprised do u know if this a common problem?
hq8aus said:
Thank you for the tutorial i will try it after few hour
I have one question : my phone refuse to enter recovery mode once the recovery mode boot the phone restart and start normally so i'm surprised do u know if this a common problem?
Click to expand...
Click to collapse
You're welcome. Xperia devices are not provided with a recovery, you need a custom one (by the way not yet available for this model).
serajr said:
You're welcome. Xperia devices are not provided with a recovery, you need a custom one (by the way not yet available for this model).
Click to expand...
Click to collapse
Thank you very much the method u wrote worked
now i'm free to install mods ? " i know it's stupid question but i'm beginner in rooting"
hq8aus said:
Thank you very much the method u wrote worked
now i'm free to install mods ? " i know it's stupid question but i'm beginner in rooting"
Click to expand...
Click to collapse
Glad to know that.
Sure you are! You can flash EdExposed and, for e.g., install my xposed modules ( Home Xposed for Q and Call Recording ).
Also any other hack you want to (my debloat script >> here << may also work).
Just a warning: due the lack of a recovery, if you face a bootloop after mess with something, you'll need to disable all the installed magisk modules to be able to boot up device, and to do so, you'll need to create a Core Mode Only magisk (google it) and fastboot it.
sorry to bother you .. but is there anyway to mount the "/system" to r/w ? because i'm having problem in moving file into it
hq8aus said:
sorry to bother you .. but is there anyway to mount the "/system" to r/w ? because i'm having problem in moving file into it
Click to expand...
Click to collapse
First of all ensure all your installed magisk modules are disabled (disable them all and reboot).
Magisk bind-mounts /system/* (specific modules folders) to do its initial mount logic, so changes into those system folders at runtime won't be allowed (if that specific system folder is used by a magisk module).
I don't know if this is your case, but I drop here this warning.
adb commands to mount system (rootfs)
rw:
Code:
mount -orw,remount /
ro:
Code:
mount -oro,remount /
You could try also to disable the vbmeta params by fastbooting vbmeta*_.img (vbmeta_*.sin > unsin.exe > vbmeta*_.img) with command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta*_.img
hi everyone,
after rooting with the boot.img patch method is there a good way to de-google the stock rom? i've seen twrp scripts for this but obviously those don't apply here, and i'm not exactly sure what is safe to remove and what is not, as a few days ago when i did this (via the /d/gapps app from f-droid) the system got stuck in a bootloop.
any ideas?
Ber7az said:
Sony's bootloader unlock page added the xperia 10 II to the list.
It's wrongly listed as "Xperia X10 II", so it's near the middle of the list, but gives the code with the IMEI
Edit:
Can't post link yet, the unlock page is: https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
Click to expand...
Click to collapse
Hi, is it possible to relock the bootloader?
Supercharlie25 said:
Hi, is it possible to relock the bootloader?
Click to expand...
Click to collapse
You could try and confirm. Xperia 1 and Xperia 5 are lockable but is not the Xperia 10, maybe the Xperia 10 II could be lockable, try on your own risk
serajr said:
As long as BL is unlocked, you may be able to root your device using XperiFirm, UnSIN and Magisk.
- XperiFirm > Download fw
- UnSIN > Get the boot_XXXX.sin file from the downloaded fw folder, and drop it over unsin.exe (you'll get boot_XXXX.img file).
- Move the boot_XXXX.img file to the device's internal storage (or sdcard).
- Install Magisk Manager app
- Magisk Manager app > Install > Uncheck 'Keep AVB 2.0/dm-verity' > Next > Select and patch a file > Choose the boot_XXXX.img (you'll get /Download/magisk_patched.img)
- Flash magisk_patched.img with fastboot with command:
Code:
fastboot flash boot magisk_patched.img
- Reboot
If something goes wrong, you'll need to flash original stock boot img file (boot_XXXX.img) with fastboot (or even flash whole fw again).
Try it at your own risk.
Click to expand...
Click to collapse
Hi, is possible flash custom Rom without recovery? I saw that it is already available for download Pixel Experience for our device. Thanks for replay.
Thapsus-cz said:
Hi, is possible flash custom Rom without recovery? I saw that it is already available for download Pixel Experience for our device. Thanks for replay.
Click to expand...
Click to collapse
I have no idea (I've never played with custom roms - stock only).
Pay attention to the 2020/08/19 build, it has a recovery image file available (as per I could see).
serajr said:
I have no idea (I've never played with custom roms - stock only).
Pay attention to the 2020/08/19 build, it has a recovery image file available (as per I could see).
Click to expand...
Click to collapse
Thank you, I'd rather wait, maybe we'll see TWRP soon.
Has anyone installed LineageOS on this?
xdauserart said:
Has anyone installed LineageOS on this?
Click to expand...
Click to collapse
The only custom ROM for our device I found Pixel Experience here https://download.pixelexperience.org/xqau52 But unfortunately I failed to flash the their recovery and twrp is not yet.
Thapsus-cz said:
The only custom ROM for our device I found Pixel Experience here ... But unfortunately I failed to flash the their recovery and twrp is not yet.
Click to expand...
Click to collapse
That doesn't sound great. I'm looking for ways to de-google it, remove tracking apps, etc. Looks like now only way is to remove apps manually via `adb`. But I'm not sure what apps to remove.
Will installing AOSP for Android 11 with Sony image be without Google apps (like Google Play and other bloat)? Did anyone try installing this? Sony has added Xperia 10 II to Open devices program recently.
@xdauserart, @Thapsus-cz, Do you know if after Unlock BL of xperia 10 II, boots with the message "Your device can't be checked by corruption. Please lock the bootloader '? And if its available some method to backup TA before, for this model? Thanks......
Hi
I recently bought a p20 lite from Facebook and i think the previous owner must have flashed the wrong firmware. In developer options there is no oem unlock button, and i tried eRecovery and it didn't work. The phone is dual sim, some apps see as if the phone is rooted and when i check with root checker, there's no root. I'm from South Africa and i hope i provided the necessary information. I would like to downgrade the phone to the firmware I'll be able to get the bootloader code from.
Looneychoons said:
Hi
I recently bought a p20 lite from Facebook and i think the previous owner must have flashed the wrong firmware. In developer options there is no oem unlock button, and i tried eRecovery and it didn't work. The phone is dual sim, some apps see as if the phone is rooted and when i check with root checker, there's no root. I'm from South Africa and i hope i provided the necessary information. I would like to downgrade the phone to the firmware I'll be able to get the bootloader code from.
Click to expand...
Click to collapse
Hi, just to be sure -
A) enter Project Menu (*#*#2846579#*#*) > 'Network info ... ' > 'Vendor country info'
B) In fastboot mode run command
fastboot oem oemimforead-CUSTOM_VERSION
and post the results.
Edit.: what was the reason for the failure with erecovery?
-Alf- said:
Hi, just to be sure -
A) enter Project Menu (*#*#2846579#*#*) > 'Network info ... ' > 'Vendor country info'
B) In fastboot mode run command
fastboot oem oemimforead-CUSTOM_VERSION
and post the results.
Edit.: what was the reason for the failure with erecovery?
Click to expand...
Click to collapse
Thanks for the reply man.
Vendor country is hw/meafnaf. Secondly, I get oeminforead-CUSTOM_VERSION failed. When i did erecovery i got 'Getting package info failed' i did factory reset and tried again but same error.
Looneychoons said:
Thanks for the reply man.
Vendor country is hw/meafnaf. Secondly, I get oeminforead-CUSTOM_VERSION failed. When i did erecovery i got 'Getting package info failed' i did factory reset and tried again but same error.
Click to expand...
Click to collapse
Okay, try this way out:
1. Download Oreo Service ROM
2. Unpack it and copy dload folder (can be found in 'Software') to the SD Card (without unpacking it!)
3. Turn of your phone and use three button combo (dload method) .
The process will erase all your data!
-Alf- said:
Okay, try this way out:
1. Download Oreo Service ROM
2. Unpack it and copy dload folder (can be found in 'Software') to the SD Card (without unpacking it!)
3. Turn of your phone and use three button combo (dload method) .
The process will erase all your data!
Click to expand...
Click to collapse
Thank you bro I'll let you know how it goes. After dload do i setup the device or wipe and factory reset, also do i check for updates or just buy credits for dc unlocker to get my bootloader code?
Looneychoons said:
buy credits for dc unlocker to get my bootloader code?
Click to expand...
Click to collapse
First check if ANE-LX2 is supported, I'm not sure...
Looneychoons said:
wipe and factory reset,
Click to expand...
Click to collapse
not necessary now
-Alf- said:
First check if ANE-LX2 is supported, I'm not sure...
not necessary now
Click to expand...
Click to collapse
Thanks man I'll kepl you posted.
-Alf- said:
First check if ANE-LX2 is supported, I'm not sure...
not necessary now
Click to expand...
Click to collapse
Hey bro I can't thank you enough. All went well after dload, I got my oem unlock button working, all that's left is to get my bootloader code. After I get it I want to root my phone, so can you please help me with a tutorial, from installing the correct twrp for my device and flashing magisk?
Looneychoons said:
Hey bro I can't thank you enough. All went well after dload, I got my oem unlock button working, all that's left is to get my bootloader code. After I get it I want to root my phone, so can you please help me with a tutorial, from installing the correct twrp for my device and flashing magisk?
View attachment 5372567View attachment 5372569
Click to expand...
Click to collapse
For Oreo only!
Download TWRP
Magisk.zip
Magisk manager apk
- download Magisk.zip and copy it to SD
- install Magisk manager apk
- install TWRP in fastboot mode, use command:
fastboot flash recovery_ramdisk TWRP-oreo-smart.img
fastboot reboot
- flash magisk.zip in TWRP
- reboot
- open M.manager apk
Update Manager & Magisk , if you want.
-Alf- said:
For Oreo only!
Download TWRP
Magisk.zip
Magisk manager apk
- download Magisk.zip and copy it to SD
- install Magisk manager apk
- install TWRP in fastboot mode, use command:
fastboot flash recovery_ramdisk TWRP-oreo-smart.img
fastboot reboot
- flash magisk.zip in TWRP
- reboot
- open M.manager apk
Update Manager & Magisk , if you want.
Click to expand...
Click to collapse
Really bro thank you. You're the best.