Finally have a rooted D5322 (T2 Ultra Dual).
Requirements:
Unlocked bootloader.
Fastboot.
boot.img with custom recovery inside. I am using boot.img from CM11, extract it from here.
SuperSU-v2.46.zip
Here is the way:
1. Activate USB debugging.
2. Flash boot.img from the link above:
Code:
flashboot flash boot.img
3. Enter recovery mode, then install UPDATE-SuperSU-v2.46.zip.
4. Flash Lollipop firmware (19.3.A.0.470) but choose kernel only to be flashed (screenshoot attached).
5. Done!
NOTE: Will be updated when I meet better internet connection. Thanks.
UPDATE (28.04.2015) : Somebody reported that /system couldn't be edited. Root explorer cant mount /system as RW.
...
Are you able to boot into recovery after flashing lollipop?
triwira said:
Finally have a rooted D5322 (T2 Ultra Dual).
Requirements:
Unlocked bootloader.
Fastboot.
boot.img with custom recovery inside. I am using boot.img from CM11, extract it from here.
SuperSU-v2.46.zip
Here is the way:
1. Activate USB debugging.
2. Flash boot.img from the link above:
Code:
flashboot flash boot.img
3. Enter recovery mode, then install UPDATE-SuperSU-v2.46.zip.
4. Flash Lollipop firmware (19.3.A.0.470) but choose kernel only to be flashed (screenshoot attached).
5. Done!
NOTE: Will be updated when I meet better internet connection. Thanks.
Click to expand...
Click to collapse
Hai.. Can you upload your extracted boot.img n give us link....
Thanks
zpr06 said:
Hai.. Can you upload your extracted boot.img n give us link....
Thanks
Click to expand...
Click to collapse
here is only the boot.img https://mega.co.nz/#!2RFBFZoR!rVrdvLSnkdfe6VS3JLUDFRLmFRtHp7hmYs2jL7hT-PY
and
https://drive.google.com/file/d/0By76vyoKsLsUQ1poSTBINWRNbWc/view?usp=sharing
What if I blink 4.4.2 kernel, use the dualrecovery by nut, do the flashes and replace only the 5.0.2 kernel rom.470, can be silly that idea, will be running? I saw that the kernel of this lollipop. 470 is 3.4.0+ as in 4.4.3,Will be running? I'm thinking of trying,Sorry for the bad English,I am using translator..
Andrey Piekas said:
here is only the boot.img https://mega.co.nz/#!2RFBFZoR!rVrdvLSnkdfe6VS3JLUDFRLmFRtHp7hmYs2jL7hT-PY
and
https://drive.google.com/file/d/0By76vyoKsLsUQ1poSTBINWRNbWc/view?usp=sharing
Click to expand...
Click to collapse
Thank you Sir! :good:
I rooted my phone following this method. Titanium Backup worked fine, but Root Explorer can't change from R/O to R/W. I think it's not rooted 100%.
rooted with this method
but can anyone give me recovery zip so i can install it.and im not able to install busybox tried so many times please help.thanks for the post...
I had the same problem, including another rom I used method like the adb, root installs, but it is not complete ... off topic, I found this rom sucks, hangs straight
thacvu said:
I rooted my phone following this method. Titanium Backup worked fine, but Root Explorer can't change from R/O to R/W. I think it's not rooted 100%.
Click to expand...
Click to collapse
vishvanjay said:
but can anyone give me recovery zip so i can install it.and im not able to install busybox tried so many times please help.thanks for the post...
Click to expand...
Click to collapse
jacitdm said:
I had the same problem, including another rom I used method like the adb, root installs, but it is not complete ... off topic, I found this rom sucks, hangs straight
Click to expand...
Click to collapse
Thread updated, I got same problem.
If you want to edit contents of /system, install boot.img from cm-12-20150226, you still can boot to homescreen and getting full root access. But some drivers not work, so you cant change brightness, using camera, etc.
When u have finish, just flash stock kernel then every thing well work.
I'm downloading this 12 cm and I do hope it works, so do root to uninstall apps that do not use and other little things, Ro / rw is so precise WHAT ... thanks for as friend... ........ .Edit.......Then I flash this kernel, flash recovery and everything, I turn on the device, delete the apps I need to delete WHAT must install and reflash standard kernel ?? That's it?Then, after flash standard kernel I lose the option to change permissions or continue? Think back as it was right? thank you
triwira said:
Thread updated, I got same problem.
If you want to edit contents of /system, install boot.img from cm-12-20150226, you still can boot to homescreen and getting full root access. But some drivers not work, so you cant change brightness, using camera, etc.
When u have finish, just flash stock kernel then every thing well work.
Click to expand...
Click to collapse
Unsuccessfully, my d5322 not care with this kernel ...
Finally I get full root. My steps are:
1. Backup data, prepare following files:
a. Flashtool from http://www.flashtool.net/downloads.php
b. "PRFCreator v0.8.zip" from http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
c. Dual recovery "T2U-lockeddualrecovery2.8.14-RELEASE.flashable.zip" from http://nut.xperia-files.com/
d. "BETA-SuperSU-v2.49.zip" from https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
e. CM11 boot image file "boot.img" from http://forum.xda-developers.com/showpost.php?p=60356750&postcount=4
f. OS 4.4.3 pre-rooted "T2 Ultra D5322.zip" from http://forum.xda-developers.com/t2-ultra/development/t2-ultra-d5303-4-4-3-pre-rooted-stock-t2962677
g. OS 5.0 ftf file "D5322_19.3.A.470_Customized IN PIEKAS.ftf" from http://forum.xda-developers.com/t2-ultra/development/5-0-2-ftf-19-3-470-d5322-t3091608
2. Use PRFCreator make flashable.zip file from OS5.0 ftf file + BETA-SuperSU-v2.49.zip + T2U-lockeddualrecovery2.8.14-RELEASE.flashable.zip like step 3 of this thread http://forum.xda-developers.com/t2-ultra/general/noobroot-lollipop-d5322-lb-ub-t3095090
3. Copy flashable.zip, T2 Ultra D5322.zip, T2U-lockeddualrecovery2.8.14-RELEASE.flashable.zip into phone
4. Flash CM11 boot.img in fastboot mode. Command: fastboot flash boot boot.img. While finish, reboot phone to recovery
5. FULL WIPE, Flash "T2 Ultra D5322.zip" and "T2U-lockeddualrecovery2.8.14-RELEASE.flashable.zip". Reboot phone normally, have rooted OS4.4.3. Can setup something and check root
6. Reboot to recovery again, flash OS5 flashable.zip file. NO WIPE
7. That's all. No issue. R/W works fine
thacvu said:
Finally I get full root. My steps are:
1. Backup data, prepare following files:
a. Flashtool from http://www.flashtool.net/downloads.php
b. "PRFCreator v0.8.zip" from http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
c. Dual recovery "T2U-lockeddualrecovery2.8.14-RELEASE.flashable.zip" from http://nut.xperia-files.com/
d. "BETA-SuperSU-v2.49.zip" from https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
e. CM11 boot image file "boot.img" from http://forum.xda-developers.com/showpost.php?p=60356750&postcount=4
f. OS 4.4.3 pre-rooted "T2 Ultra D5322.zip" from http://forum.xda-developers.com/t2-ultra/development/t2-ultra-d5303-4-4-3-pre-rooted-stock-t2962677
g. OS 5.0 ftf file "D5322_19.3.A.470_Customized IN PIEKAS.ftf" from http://forum.xda-developers.com/t2-ultra/development/5-0-2-ftf-19-3-470-d5322-t3091608
2. Use PRFCreator make flashable.zip file from OS5.0 ftf file + BETA-SuperSU-v2.49.zip + T2U-lockeddualrecovery2.8.14-RELEASE.flashable.zip like step 3 of this thread http://forum.xda-developers.com/t2-ultra/general/noobroot-lollipop-d5322-lb-ub-t3095090
3. Copy flashable.zip, T2 Ultra D5322.zip, T2U-lockeddualrecovery2.8.14-RELEASE.flashable.zip into phone
4. Flash CM11 boot.img in fastboot mode. Command: fastboot flash boot boot.img. While finish, reboot phone to recovery
5. FULL WIPE, Flash "T2 Ultra D5322.zip" and "T2U-lockeddualrecovery2.8.14-RELEASE.flashable.zip". Reboot phone normally, have rooted OS4.4.3. Can setup something and check root
6. Reboot to recovery again, flash OS5 flashable.zip file. NO WIPE
7. That's all. No issue. R/W works fine
Click to expand...
Click to collapse
is all your root app's working fine till now?
no bootloop & other issues?
not root dear.
triwira said:
Finally have a rooted D5322 (T2 Ultra Dual).
Requirements:
Unlocked bootloader.
Fastboot.
boot.img with custom recovery inside. I am using boot.img from CM11, extract it from here.
SuperSU-v2.46.zip
Here is the way:
1. Activate USB debugging.
2. Flash boot.img from the link above:
Code:
flashboot flash boot.img
3. Enter recovery mode, then install UPDATE-SuperSU-v2.46.zip.
4. Flash Lollipop firmware (19.3.A.0.470) but choose kernel only to be flashed (screenshoot attached).
5. Done!
NOTE: Will be updated when I meet better internet connection. Thanks.
UPDATE (28.04.2015) : Somebody reported that /system couldn't be edited. Root explorer cant mount /system as RW.
...
Click to expand...
Click to collapse
not working brother
help me to rrot my d5322
triwira said:
Finally have a rooted D5322 (T2 Ultra Dual).
Requirements:
Unlocked bootloader.
Fastboot.
boot.img with custom recovery inside. I am using boot.img from CM11, extract it from here.
SuperSU-v2.46.zip
Here is the way:
1. Activate USB debugging.
2. Flash boot.img from the link above:
Code:
flashboot flash boot.img
3. Enter recovery mode, then install UPDATE-SuperSU-v2.46.zip.
4. Flash Lollipop firmware (19.3.A.0.470) but choose kernel only to be flashed (screenshoot attached).
5. Done!
NOTE: Will be updated when I meet better internet connection. Thanks.
UPDATE (28.04.2015) : Somebody reported that /system couldn't be edited. Root explorer cant mount /system as RW.
...
Click to expand...
Click to collapse
is this method work on 19.3.A.0.472
Related
I saw this in facebook group "xperia t3 - india".. it seems we just need the camera to work
and 4G, and sdcard1...
vmlc said:
I saw this in facebook group "xperia t3 - india".. it seems we just need the camera to work
Click to expand...
Click to collapse
Hi i'm the guy how have cyanogen on my T3 , I just wanted to warn you for the rom, select the FXP-cm12-20150412...
And not the FXP-cm12.1 ...
otherwise your phone will bootloop, and when you make the first start of the phone , don't worry if after the bootanimation there's a black screen just wait 2-3 minutes for the update
So enjoy Cyanogen Xperia Users
fastbooking said:
Hi i'm the guy how have cyanogen on my T3 , I just wanted to warn you for the rom, select the FXP-cm12-20150412...
And not the FXP-cm12.1 ...
otherwise your phone will bootloop, and when you make the first start of the phone , don't worry if after the bootanimation there's a black screen just wait 2-3 minutes for the update
So enjoy Cyanogen Xperia Users
Click to expand...
Click to collapse
so, you confirm no 4g and camera working?
vmlc said:
so, you confirm no 4g and camera working?
Click to expand...
Click to collapse
yes no camera and 3G/4G
fastbooking said:
yes no camera and 3G/4G
Click to expand...
Click to collapse
also, you should do a detailed tutorial how to try the seagull build, i tried it the other day, but I couldnt do it....
vmlc said:
also, you should do a detailed tutorial how to try the seagull build, i tried it the other day, but I couldnt do it....
Click to expand...
Click to collapse
I will try tomorow there's a french tutorial about that here's the link for the one's who speak french
phonandroid.com/forum/post1800321.html (www . before its just because i can't now)
Cyanogen ROM are distributed in zip format, so you have to :
- push the zip file to your sdcard
- you need a kernel with recovery (for the time being, the Philz one)
- you enter in recovery mode
- you select "install zip" and the zip file.
once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot
reboot and enjoy
dan15 said:
Cyanogen ROM are distributed in zip format, so you have to :
- push the zip file to your sdcard
- you need a kernel with recovery (for the time being, the Philz one)
- you enter in recovery mode
- you select "install zip" and the zip file.
once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot
reboot and enjoy
Click to expand...
Click to collapse
ok, the part I dont get is: "once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot"
how do you do this?
dan15 said:
Cyanogen ROM are distributed in zip format, so you have to :
- push the zip file to your sdcard
- you need a kernel with recovery (for the time being, the Philz one)
- you enter in recovery mode
- you select "install zip" and the zip file.
once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot
reboot and enjoy
Click to expand...
Click to collapse
I don't install cyanogen like that,
First I update my phone with EMMA with the Open devices TA
-After I open the zip of the rom and i extract it somewhere you can find it
-take the zip AND THE GAPPS and connect your phone on usb for sending the zip on THE ROOT of your sdcard
-Enter in fastboot, and open flashtool (not emma the other)
-Flash the kernel called : boot.img
-Once Flashed reboot your phone in recovery (up button when the led is purple or violet)
-The led became gold color
- You now are (normaly) in cyanogen recovery
-Wipe data/Factory reset
-Wipe Cache for avoid bugs
-Now the fun part
-Apply update select the ROM and after the GAPPS
-Reboot and enjoy !
If the screen is black for a while after boot it's normal it's the system update
I also recommand you to take the
FXP-cm-12-20150412-UNOFFICIAL-seagull.zip
file because the other in cm12.1 are bootlooping
Now you can enjoy properly without camera and 3G/4G cyanogen
Sorry for my english I'm just a 14 french kid
btw, is this for 5102 or 5103? also, what do I have to be installed on my computer so I can flash boot for fastboot?
vmlc said:
btw, is this for 5102 or 5103? also, what do I have to be installed on my computer so I can flash boot for fastboot?
Click to expand...
Click to collapse
This is for D5103 the D5102 isn't the seagull this name is ONLY for the D5103
For the manipulation you will need emma (called flashtool by sony,for updating the bootloader)
And flashtool by Androxyde (this only is for flash kernel)
:highfive: now you're ready
Enjoy cyanogen on our t3 :laugh:
fastbooking said:
This is for D5103 the D5102 isn't the seagull this name is ONLY for the D5103
For the manipulation you will need emma (called flashtool by sony,for updating the bootloader)
And flashtool by Androxyde (this only is for flash kernel)
:highfive: now you're ready
Enjoy cyanogen on our t3 :laugh:
Click to expand...
Click to collapse
Im having problems flashing the kernel. I cant find my device in fastboot, and when I use flashtool to go ADB mode it says I dont have usb debugging on because I installed zip from recovery, the seagull file...
vmlc said:
Im having problems flashing the kernel. I cant find my device in fastboot, and when I use flashtool to go ADB mode it says I dont have usb debugging on because I installed zip from recovery, the seagull file...
Click to expand...
Click to collapse
Ok let's start off zero
you installed the zip via the philz recovery and after you wanted to flash the kernel ?
dan15 said:
Cyanogen ROM are distributed in zip format, so you have to :
- push the zip file to your sdcard
- you need a kernel with recovery (for the time being, the Philz one)
- you enter in recovery mode
- you select "install zip" and the zip file.
once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot
reboot and enjoy
Click to expand...
Click to collapse
thats what it says...
vmlc said:
thats what it says...
Click to expand...
Click to collapse
follow my tutorial it's the steps i followed and it works for me :good:
fastbooking said:
follow my tutorial it's the steps i followed and it works for me :good:
Click to expand...
Click to collapse
I got bricked meanwhile. Battery problem I think, not the first time...
ok, i think there is a missunderstanding.
in order to flash the kernel, you need to be in fastboot mode (with the blue light). so, once you have installed the zip file, shut down the phone (in recovery mode, select "power options/power off" , disconnect the phone and reconnect it in fastboot (maintain the vol up before and during the USB connection ).
you can now use "flashtool" (the Androxyde's one. to avoid confusion, the Sony's one is called EMMA or if it is more easy for you fastboot.exe
to use fastboot, you open a command line (Windows+R + type "cmd") , you go to the folder where the boot.img is and you enter the comand "fastboot flash boot boot.img". after ~2s the kernel is flashed, you can disconnect the phone and restart.
the first time, the boot time is about 5 min with a black screen after the animated screen, so wait a moment.
it's for that it's very important to have a well charged phone (min 40%) because the first start use a lot of battery, and you can't see anything.
I want to restore, I just installed the zip. Why cant I enter recovery?
edit: ok, I entered cyanogen recovery. will try to boot now. but I dont have backup/restore option....
edit2: ok, It booted but I still want to know how to back to previous version...
vmlc said:
I want to restore, I just installed the zip. Why cant I enter recovery?
edit: ok, I entered cyanogen recovery. will try to boot now. but I dont have backup/restore option....
edit2: ok, It booted but I still want to know how to back to previous version...
Click to expand...
Click to collapse
go on emma and select the android 4.4.4 update KK in the services line under open devices TA
It will restore the like the 1 st day but you will loose your data, but after you can install the philz recovery and restore the backup
Yes,its working...
REMOVE ALL OTHER ROOT...working or not befor installing magisk....may end with....something you dont want...
Maybe it would be best to start with a freshly factory resetted phone.... (anyway,to erase all errors in TWRP,youll format/data so... )
you need bootloader unlock... followed instructions HERE don't forget to OEM UNLOCK in /settings/Developer section on phone..(enable it while pressing repeatedly on Phone version (in ''about phone also in settings)
You need MINIMAL ADB on pc...HERE
You need TWRP recovery installed...HERE
but before doing all that...BE SHURE to have the original UPDATE.APP (firmware from huawei) somewhere on your pc
you will need the BOOT.img from your original firmware... (extract it from the update.app (update.zip for huawei firmware)
HERE
extract the boot.img somewhere on your pc... like on your desktop...
then,youll need 2 magisk things...
the LATEST magisk ZIP file...
and the LATEST MAGISK APK...
FOLLOW THESE INSTRUCTIONS (from Magisk post...i did it and its working :silly: )
Installation Instructions
If you already have Magisk installed, you can directly upgrade through Magisk Manager
For installing Magisk the first time
Make sure to remove any other root, best to restore your boot image back to stock
Via custom recovery:
Download the latest Magisk zip file
Reboot to a custom recovery and flash the flashable zip
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually
the ADB method is the best...
after reboot,in magisk app,youre supposed to be GREEN checked....
after that,if all green,you can FIX that DATA problem in TWRP...saying cant mount or blablabla...
DO a backup cuz yess,youll loose everything... Hisuite for your apps
in twrp, FORMAT DATA... ...wipe data factory reset...re install your things then,youll be able to do recoverys ect. in twrp
dont forget to RE INSTALL magisk APK after formatting and factory reset
IT WILL take some time TO BOOT... so let it do its thing...
Now about magisk modules...all of them ive tried ended in (blablabla not a magisk module)...
no big deal....just dload the zip and look for the app or file in it... and apply to where it belongs... like new Oreo Emojis...ive dloaded the zip,found the file, then paste the file in /system/fonts...then reboot
now...if i made a mistake somewhere in my explanations well... sorry....
WARNING
IF youre device is bricked or what so ever... its not MY fault....you do that on your own......Ive done it,followed MAGISK instructions and its working....
Not shure about it...DONT DO IT....
DON'T DO TWRP backups with fingerprints/nip/code unlock methods activated on your phone... i had to factory reset phone cuz code was not working.
YES there's a way to recover anyway... THANKS HENKATE
Regarding fingerprint, boot in recovery and go to advanced > file manager and delete data/system/locksettings.db
Then advanced > terminal and type:
cd data/system
rm -rf *.key
Then reboot and you won't have secured lockscreen
MAGISK modules are HERE
Magisk MANAGER is available on PLAYSTORE
BEFORE making a twrp backup... (after data format ect.)...
you may want to FIX the huawei theme manager not working problem for some of us... the FIX is HERE
Thanks to Henkate
Youll need a good file system manager...i'm using ROOT EXPLORER and theres that new FX file explorer
does it work with android 7?
tanlikar1 said:
does it work with android 7?
Click to expand...
Click to collapse
Yes. In fact, this was meant for Android 7, but it should work on Android 6 too.
Absolutely...Im on Nougat emui5
does anyone have stock rom for MLA-L12C636B340 ?
Do you mean original firmware ?
Maybe you can still get it via firmware finder...
virusdunil said:
Do you mean original firmware ?
Maybe you can still get it via firmware finder...
Click to expand...
Click to collapse
ya
Working on Nova?
Does it work in the non plus Nova as well? Any experiences?
Worked on Can-L11. Tested. No need format data, in twrp tree, i add img, that work with encrypted data.
I can't get this to work on my MLA-03, i have TWRP installed and unlocked b/l. I tried to flash RR and Lineage but getting "can't mount" errors up the ying yang. Anyone with MLA-03 got any tips? Is there a certain recovery that is recommended?
Cooks_08 said:
I can't get this to work on my MLA-03, i have TWRP installed and unlocked b/l. I tried to flash RR and Lineage but getting "can't mount" errors up the ying yang. Anyone with MLA-03 got any tips? Is there a certain recovery that is recommended?
Click to expand...
Click to collapse
hi...yes and its a bit confusing...but,just follow instructions for LOS install...forget about /mount data and after flashing ,just reboot
virusdunil said:
hi...yes and its a bit confusing...but,just follow instructions for LOS install...forget about /mount data and after flashing ,just reboot
Click to expand...
Click to collapse
Got the flash working. Used Garak's Twrp and now i got. Thanks.
Does it work for android 8.0 or Huawei nova 2s in particular? I did make unlock the bootloader, but i could not find reliable root method. Please help with advice. Thank you.
Mezo21 said:
Does it work for android 8.0 or Huawei nova 2s in particular? I did make unlock the bootloader, but i could not find reliable root method. Please help with advice. Thank you.
Click to expand...
Click to collapse
Hi there,
I have Nova 2s, carefully follow this thread's instructions, it will 100% works : https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
Thanks for the guidance, Magisk is doing very well.
Only TWRP is missing, but later.
Huawei Nova
CAN-L01C432B382
Magisk modules not working even if i rooted. Cant install modules from magisk app and twrp .zip
meskafonas said:
Magisk modules not working even if i rooted. Cant install modules from magisk app and twrp .zip
Click to expand...
Click to collapse
did you format data as f2fs? If yes, magisk doesn't go well along with it. If no, then you would get better support at magisk thread
virusdunil said:
Yes,its working...
REMOVE ALL OTHER ROOT...working or not befor installing magisk....may end with....something you dont want...
Maybe it would be best to start with a freshly factory resetted phone.... (anyway,to erase all errors in TWRP,youll format/data so... )
you need bootloader unlock... followed instructions HERE don't forget to OEM UNLOCK in /settings/Developer section on phone..(enable it while pressing repeatedly on Phone version (in ''about phone also in settings)
You need MINIMAL ADB on pc...HERE
You need TWRP recovery installed...HERE
but before doing all that...BE SHURE to have the original UPDATE.APP (firmware from huawei) somewhere on your pc
you will need the BOOT.img from your original firmware... (extract it from the update.app (update.zip for huawei firmware)
HERE
extract the boot.img somewhere on your pc... like on your desktop...
then,youll need 2 magisk things...
the LATEST magisk ZIP file...
and the LATEST MAGISK APK...
FOLLOW THESE INSTRUCTIONS (from Magisk post...i did it and its working :silly: )
Installation Instructions
If you already have Magisk installed, you can directly upgrade through Magisk Manager
For installing Magisk the first time
Make sure to remove any other root, best to restore your boot image back to stock
Via custom recovery:
Download the latest Magisk zip file
Reboot to a custom recovery and flash the flashable zip
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually
the ADB method is the best...
after reboot,in magisk app,youre supposed to be GREEN checked....
after that,if all green,you can FIX that DATA problem in TWRP...saying cant mount or blablabla...
DO a backup cuz yess,youll loose everything... Hisuite for your apps
in twrp, FORMAT DATA... ...wipe data factory reset...re install your things then,youll be able to do recoverys ect. in twrp
dont forget to RE INSTALL magisk APK after formatting and factory reset
IT WILL take some time TO BOOT... so let it do its thing...
Now about magisk modules...all of them ive tried ended in (blablabla not a magisk module)...
no big deal....just dload the zip and look for the app or file in it... and apply to where it belongs... like new Oreo Emojis...ive dloaded the zip,found the file, then paste the file in /system/fonts...then reboot
now...if i made a mistake somewhere in my explanations well... sorry....
WARNING
IF youre device is bricked or what so ever... its not MY fault....you do that on your own......Ive done it,followed MAGISK instructions and its working....
Not shure about it...DONT DO IT....
DON'T DO TWRP backups with fingerprints/nip/code unlock methods activated on your phone... i had to factory reset phone cuz code was not working.
YES there's a way to recover anyway... THANKS HENKATE
Regarding fingerprint, boot in recovery and go to advanced > file manager and delete data/system/locksettings.db
Then advanced > terminal and type:
cd data/system
rm -rf *.key
Then reboot and you won't have secured lockscreen
Click to expand...
Click to collapse
Do you have this problem with fingerprint? [emoji853] https://r.tapatalk.com/shareLink?ur...share_tid=3907398&share_fid=3793&share_type=t
Enviado desde mi HUAWEI CAN-L11 mediante Tapatalk
Hello hello,
this will be my "live" thread of bringing AICP 13.1 to my xperia z1c, I found some Guide's that I will follow and I will share with you all the links and knowledge I gained as a newbie that I used to understand and fix my problems on the way.
Maybe this will help you, too.
Main Tutorial: LINK
Target of all this: LINK
My Device:
Sony XPERIA Z1C, 14.6.A.1.236 , Lollipop 5.1.1
My best hint: read carefully, take your time to understand what you're trying to do and do your own research!
Hopefully you will get a aicp custom rom out of it.
_____________________________________________
_____________________________________________
General information: Android 5.1.1 cannot be rooted due to its high security standards, therefore we will downgrade to a lower security stock rom and create root access there. Root access will be needed as well as an unlocked bootloader to install real recovery (TWRP) which is the tool to flash custom roms like aicp. But the aicp custom rom will not have a good working camera, don't ask me why, but the camera seems to be a really difficult thing from the point of developer's view, let's accept this. Aside of that disadvantage, this custom rom is a very nice software and it makes my z1c kind of new. I don't use my camera anyway often at all.
During all this flashing thing I had a very big ??? while implementing real recovery. I was able to flash the .236.ftf but not the openbootloader.ftf as described in section 5 in the main tutorial. The result was twrp boot failed.
Error description:
flash .236.ftf works
flash openbootloader fails
flash twrp works
boot twrp fails
boot stock rom works
My solution:
I restarted from scratch and finally with the kind of messed up secquenceI got it:
flash .236.ftf works
flash openbootloader fails
flash twrp works
boot twrp fails
flash openbootloader works
flash twrp works
boot twrp works
UPDATE 06.12.2018 as a solution for REAL RECOVERY with working camera <<< RECOMMENDED
0. boot into rom works
1. flash openbootloader works
2. boot into rom works
3. flash .236.ftf works
4. boot into rom & check camera works
3. flash twrp ( business as usal ) works
4. boot twrp ( First boot is damn important, don't miss it! Press Vol- & Power, wait for vibration, release Power & keep Vol- until twrp boots up ) works
5. full wipe, flash aicp-rom, flash gapps, flash magisk-root, boot system works
6. enjoy Oreo 8.1 & camera check !!! works !!!
This routine worked straight forward for me where I started from scratch with my second device.
Flashing aicp was pretty easy, good to know for flashing the rom was full wipe = advanced wipe and select everything except of micro sd
To complete my aicp 13.1 Oreo 8.1 device the camera problem has to be fixed ( Saving the taken picture fails, display goes into freeze, no chance to solve this with camera mods, camera apps )
But @lm089 gave me the right hint, and finally this was my solution! Thanks again @lm089!!
Have fun with your new >> SONY XPERIA Z1 COMPACT <<
How to update TWRP
1. Turn Off your device
2. Start device in fastboot mode by connecting via usb cable to your pc and press Vol- until blue led tuns on
3. use fastboot flash recovery twrp.img to flash it
4. boot twrp ( This first boot is damn important, don't miss it! Press Vol- & Power, wait for vibration, release Power & keep Vol- until twrp boots up ) works
How to update to aicp 14.0 pie 9.0
starting with the running and latest aicp 13.1 oreo 8.1 rom above I just followed the Instructions here. As a specialty I had to install the Magisk Manager App manually into the rom to get root. Downloading supersu.apk from www.supersuroot.org works fine as well.
Your fastboot connection doesnt work for some reason though u had this workin fine in the past? maybe u had a windows update. install your drivers again.
>> LETS KEEP THIS DEVICE ALIVE <<
_____________________________________________
_____________________________________________
More helpful links that I used:
Debug apps by creating logs
what is adb? an xda tutorial
ADB working Download Link and ADB Article on xda
xda flashtool error during setup: click
[NOOBIE] Basic adb commands and device partition overview
Latest TWRP 3.2.3-0 for z1c
root solution using flash tool
Restore DRM functionality after UB
If TA Backup dry restoration restoration fails: Solution and Download *.dll
Boot into recovery or fastboot mode
How to install TWRP
Magisk beats superSU
How to Install Custom ROM using TWRP for Android!
change boot animations
[TUTORIAL] Design Your Own Bootanimation
Backup & Restore Your ROM With TWRP
Terminology: odex and deodex
If the camera goes into freeze or saving the picture fails: This was my solution! /// But you better go straight with the steps of my update 06.12.2018, field tested!
THANKS A LOT TO @colaigor for his [BEGINNERS GUIDE]
Ok. So i dont have much time now but i can give some short directions.
1. Get unlock codes from sony for bootloader unlock
2. Instal adb and fastboot at your system(PC)
3. Instal z1c drivers
4. Instal flashtool
5. Unlock bootloader,root,flash recovery(search forum for "real recovery" ),flash root solution
6. Flash wanted rom,gaps
P.P. On second thought u dont need flashtool. All can be done with adb and fastboot commands from terminal
There is one thing I don't understand:
what is the difference between FLASHING REAL RECOVERY and FLASHING FAKE RECOVERY?
What I read is, that in both cases I get TWRP but on different partitions (real = Recovery Partition, fake = Boot partition) but do I need both or do I choose just on of them?
derjango said:
There is one thing I don't understand:
what is the difference between FLASHING REAL RECOVERY and FLASHING FAKE RECOVERY?
What I read is, that in both cases I get TWRP but on different partitions (real = Recovery Partition, fake = Boot partition) but do I need both or do I choose just on of them?
Click to expand...
Click to collapse
Real recovery have its own partition(after that update to bootloader). Custom recovery dont have that and its stored somewhere else(FOTA,onetime boot image , etc). Choose real recovery. New stuff works good with it.
Ok thank you :good:
flashtool log of openbootloader.ftf failed:
01/015/2018 13:15:58 - INFO - Device connected in flash mode
01/017/2018 13:17:19 - INFO - Selected Bundle for Sony Xperia Z1 Compact(D5503). FW release : 1. Customization : openbootloader
01/017/2018 13:17:19 - INFO - Preparing files for flashing
01/017/2018 13:17:19 - INFO - Please connect your device into flashmode.
01/017/2018 13:17:19 - INFO - Using Gordon gate drivers version 3.1.0.0
01/017/2018 13:17:20 - INFO - Opening device for R/W
01/017/2018 13:17:20 - INFO - Device ready for R/W.
01/017/2018 13:17:20 - INFO - Reading device information
Click to expand...
Click to collapse
solved, I skipped step 5.2, flashing the .236.ftf in advance
but how can I start TWRP?
doesnt work with POWER + Vol-, vibrate & release power
I tried to flash the following recovery solution using this command:
smartphone in fastboot mode (blue LED enabled)
fastboot flash recovery recovery.img
TWRP from step 5.1 of the GUIDE
TWRP 3.0.2
My formerly flashed .236.ftf rom works fine, but I cant start TWRP the device goes directly to my rom
zlata said:
Real recovery have its own partition(after that update to bootloader). Custom recovery dont have that and its stored somewhere else(FOTA,onetime boot image , etc). Choose real recovery. New stuff works good with it.
Click to expand...
Click to collapse
Thats where I'm stuck right now, any ideas how to fix?
okay got it, basically i do not know what the problem is but:
after BLU
flash .236 :good:
flash openbootloader
flash twrp :good:
--> failed to install openbootloader and probably thus twrp failed
solution: I skipped to flash .236 as recommended by the author of the GUIDE (step 5.2)
flash open bootloader :good:
flash twrp :good:
--> failed to start twrp, though it was installed successfully
flash .236 :good:
flash openbootloader (failed again, but it's already on the device and I guess I could have skipped this here)
flash twrp :good:
first boot of twrp is successful :good:
And basically the author explained it in his text, FIRST INSTALL OPEN BOOTLOADER BEFORE WRITING STH TO RECOVERY PARTITION
I think you should use Aicp 14 pie instead of 13.1 Oreo
I feel Aicp 14 PIE is very stable and flash port camera stock this link https://forum.xda-developers.com/crossdevice-dev/sony-themes-apps/port-stock-camera-nougat-roms- t3628791
Nice thread, thank you! Wish I had that when I started rooting and flashing
@lm089 Haha it's quite some work to get into it, right? I just saw that we are running on the same device & custom rom, how did you solve the issue with the not working camera? I'm still reading stuff about some mod, but I'm curious and open for tested solutions on z1c
best, dj
derjango said:
how did you solve the issue with the not working camera? I'm still reading stuff about some mod, but I'm curious and open for tested solutions on z1c
best, dj
Click to expand...
Click to collapse
Had this situation twice with 2 different oreo ROMs. Both times I solved it following a rather strange sounding suggestion I found on the AICP 13.1 discussion thread. The basic idea is to go back to a stock Sony ROM. Boot into it and make sure the camera is working which for me was the case both times. Then - if necessary - re-root your phone (on first occasion I flashed a pre-rooted .236 version but that caused some extra trouble so next time I decided to flash an unrooted version). And from then on it's the standard way as you described it in your OP.
Good luck!
Okay, thanks a lot for your hint! Unfortunately the camera mod didn't fix the problem, my android-task for this evening is defined:
AICP 13.1 Oreo 8.1 on z1c, root, ulb, magisk 17.1
1. backup my system (done)
2.0 flash stock rom lollipop 5.1.1 (14.6.A.1.236.ftf) with flashtool via usb (done),booting the os for the first time takes quite long (~10m), check camera in the os (done)
interesting fact: recovery is deleted by flashing the rom via flashtool - I thought I can go the lazy way and skip the step of installing twrp again into recovery
2.1 okay, let's do it: install twrp (done) and boot into twrp, NOT into ROM!! (done) (Vol- & Power, wait for vibration & release Power but keep Vol- until TWRP starts up)
3. flash aicp 13.1 following this (full wipe as an advanced wipe: select all EXCLUDING THE SD STORAGE)
Again here, I recognized the first boot of the rom takes quite longer.
4. check camera (done)
!!!! IT WORKS !!!!
(I did it two times)
alright, lets start flashing my second device - now I know how to do it
Thanks guys!!
derjango said:
!!!! IT WORKS !!!![/SIZE]
Click to expand...
Click to collapse
Weird, isn't it?
lm089 said:
Weird, isn't it?
Click to expand...
Click to collapse
Totally But hey, it's a solution
btw @lm089, boots your ota-updater directly into twrp and start the flashing procedure? In my case I had to boot twrp manually and flash the zip manually, too
derjango said:
btw @lm089, boots your ota-updater directly into twrp and start the flashing procedure? In my case I had to boot twrp manually and flash the zip manually, too
Click to expand...
Click to collapse
No, updater is booting into recovery, doing a nandroid backup and wiping caches (because I told it to), then flashing and finally rebooting into system. All by itself :good:
I remember having trouble with that in the past though. Do you by any chance have an SD card formatted as adoptable storage?
lm089 said:
No, updater is booting into recovery, doing a nandroid backup and wiping caches (because I told it to), then flashing and finally rebooting into system. All by itself :good:
I remember having trouble with that in the past though. Do you by any chance have an SD card formatted as adoptable storage?
Click to expand...
Click to collapse
Yes, its used as an external storage
derjango said:
Yes, its used as an external storage
Click to expand...
Click to collapse
ok, that's something different; adoptable storage means that your SD or part of it is setup to extend internal storage. If you can access all of your SD from TWRP then it is indeed formatted a external storage.
1) How to unlock bootloader:
https://developer.sony.com/develop/...ed/unlock-bootloader/how-to-unlock-bootloader
2) Download Platform-tools (adb & fastboot) r.26.0.2 as latests version does not work (or just for me):
https://xiaomifirmware.com/downloads/download-platform-tools-adb-fastboot-r-26-0-0/
3) Download TWRP 3.2.3-0 https://androidfilehost.com/?fid=11410963190603854057 and place file in Platform Tools folder on PC
4) Restart in fastboot mode and flash revovery:
fastboot flash recovery Z1C_twrp_3.2.3-0.img
fastboot reboot
5.1) Download AICP Oreo 8.1 http://dwnld.aicp-rom.com/device/amami/WEEKLY/aicp_amami_o-13.1-WEEKLY-20181204.zip and place file in Platform Tools folder on PC
5.2) Download Gapps Pico https://opengapps.org/?download=false&arch=arm&api=8.1&variant=pico and place file in Platform Tools folder on PC
5.3) Download stable Magisk 17.1 https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip place file in Platform Tools folder on PC
6.1) Load TWRP. Advance>ADB Sideload (for Oreo)
adb sideload aicp_amami_o-13.1-WEEKLY-20181204.zip
(do not restart)
6.2) Repeat Advance>ADB Sideload (for Gapps)
adb sideload open_gapps-arm-8.1-pico-2018XXXX.zip
(do not restart)
6.3) Repeat Advance>ADB Sideload (for Magisk)
adb sideload Magisk-v17.1.zip
(restart)
TWRP 3.3.1 & Root for Moto 1 VisionThanks to the efforts of yuri-2016 and and my humble contribution, the TWRP 3.3.1 was made from scratch and a new method of Root was tested.
Accept this gift from the bottom of your heart! :highfive:
Instructions
USB debugging must be enabled on the phone and the bootloader must be unlocked!
1. Download attached archive TWRP_Root_Motne_Vision.zip and extract files from it in the following order::
- .bat executive file and vbmeta.img to the folder with the firmware files;
- TWRP-3.3.1_Motorola_One_Vision.img to \adb\ folder.
- TWRP-3.3.1_Installer_Motorola_One_Vision.zip, Disable_Dm-Verity_ForceEncrypt.zip, Magisk Installer, MagiskManager copy to External SDcard in your phone.
2. Load phone in fastboot mode, then connect it to PC, then start an executive file .bat. At the end of flashing the phone will reboot into bootloader-mode and then TWRP again.
3. In the Recovery at the very beginning we put a checkmark in the checkbox to avoid this request in future, and give permission to modify the system for writing.
4. Go to the Wipe page and run the Format Data for decryption. Enter "yes" for the request. Exit to the Main Menu and reboot to Bootloader.
5. Attention! You mus BOOT into Recovery mode (DO NOT INSTALL it !), through the command:
Code:
fastboot boot C:\adb\TWRP-3.3.1_Motorola_One_Vision.img
6. Flash an archive TWRP-3.3.1_Installer_Motorola_One_Vision.zip which will make TWRP permanent.
NOTE: If you want to keep the stock Recovery , do not install this archive, but in order to boot into TWRP you will need to run the command from Step 5 every time.
7. Configure TWRP via “Settings”-page (time, time zone, language, etc.) as you want.
8. Go to “Install” page and flash the Magisk Installer , and flash Disable_Dm-Verity_ForceEncrypt.zip
9. Reboot in System. Phone will reboot several times, don`t worry. Perform initial settings again.
10. Install MagiskManager.apk, because the application installed in the system generates an error and does not start.
Now your device has a custom recovery TWRP and Root rights! :good: :victory:
01/10/2019 New instruction have been made
30/09/2019 New build TWRP !!!
Fixed: Removed the "Enable MTP" button.
Note: Who will reinstall the new TWRP build over the old one, follow these steps:
1. Download new TWRP_Root_Motne_Vision.zip
2. Load into Recovery mode via the command:
Code:
fastboot boot C:\adb\TWRP-3.3.1_Motorola_One_Vision.img
3. Install TWRP-3.3.1_Installer_Motorola_One_Vision.zip
4. Flash Magisk installer, Disable_Dm-Verity_ForceEncrypt.zip.
5. Reboot in the Recovery again.
6. Try to adjust the brightness, connect USB-OTG, check the absence of the "Enable MTP" button.
Old instructions
Friends! I got the Root for this device.
I'm not saying it's the only way to get a Root. I suggest something I used on my own device.
You are responsible for everything you do with your device!
Getting Root was performed on firmware XT1970-3_KANE_RETEU_DS_9.0_PSA29.160-30
Attention! The process of receiving the Root will delete all your data from the device.
1. The bootloader must be unlocked on the device beforehand.
2. Extract files from the archive https://drive.google.com/open?id=1xgTVlIXOFWq59I1-D9bnRlj1heJycT_I :
- vbmeta.img, vbmeta_patch.img and boot_patch.img to the adb folder;
- MagiskManager-v7.3.4.apk to a convenient folder for you. It will then need to be copied either to the phone memory or to the SD Card.
3. Load the device into fastboot mode and connect it to your PC.
4. Flash vbmeta.img with the command:
Code:
fastboot flash vbmeta_a vbmeta.img
5. Flash boot_patch.img with the command:
Code:
fastboot flash boot_a boot_patch.img
6. Flash vbmeta_patch.img command:
Code:
fastboot flash vbmeta_a vbmeta_patch.img
7. Load the device into the system by pressing the Start button. Phone will reboot in Recovery where there will be a warning that it is necessary to execute Factory reset. It is necessary to give your consent.
The phone will reboot several times again, don't worry.
8. Perform the initial setup. Install MagiskManager-v7.3.4.apk.
9. Launch the MagiskManager application. He will offer to update the application, click the Yes button. The phone will reboot.
Your device now has Root permissions and access to the system!
ilia3367 said:
Friends! I got the Root for this device. Tomorrow I will try to describe in detail the process of getting the Root.
Click to expand...
Click to collapse
Thank you so much!
That's incredible. I hope it works on Moto One Action too.
ilia3367 said:
Friends! I got the Root for this device. Tomorrow I will try to describe in detail the process of getting the Root.
Click to expand...
Click to collapse
This is excellent news, thanks !
Unlock the bootloader
Download the stock rom
Install magisk manager
Click install and chose patch boot image
Copy the patched boot image to your PC
Flash the new image using ADB
I think these are the steps to root the phone
SnoopDoggyStyleDogg said:
Unlock the bootloader
Download the stock rom
Install magisk manager
Click install and chose patch boot image
Copy the patched boot image to your PC
Flash the new image using ADB
I think these are the steps to root the phone
Click to expand...
Click to collapse
Those step give you the validation img error
I'm continuing with my friend to create TWRP
SnoopDoggyStyleDogg said:
Unlock the bootloader
Download the stock rom
Install magisk manager
Click install and chose patch boot image
Copy the patched boot image to your PC
Flash the new image using ADB
I think these are the steps to root the phone
Click to expand...
Click to collapse
That's what a lot of people think. I thought so too.
Thank you so much for the guide... I'll try in the afternoon
@ilia3367
Hello
I have a One Action, could you help me to get root?
Do I need to patch all those images with Magisk?
Thanks in advanced.
sfoot13 said:
@ilia3367
Do I need to patch all those images with Magisk?
Click to expand...
Click to collapse
Make a modified boot.img with Magisk and take my other files. Try to do it according to the instructions.
ilia3367 said:
Make a modified boot.img with Magisk and take my other files. Try to do it according to the instructions.
Click to expand...
Click to collapse
Thank you so much for your help and work!
I'll do that when I arrive at home
Hey! That's really good news pal. Do you think I can flash your Vision's vbmeta.img and vbmeta_patch.img and my magisk-patched boot.img on my Motorola One Action?
Tuandroidaldia said:
Hey! That's really good news pal. Do you think I can flash your Vision's vbmeta.img and vbmeta_patch.img and my magisk-patched boot.img on my Motorola One Action?
Click to expand...
Click to collapse
Replied on the previous page.
ilia3367 said:
Replied on the previous page.
Click to expand...
Click to collapse
Nope, it's not working on Motorola One Action, it says: "<bootloader> validation image failed" using my Magisk Patched Boot.img. Did you patched your boot using another tool or how?
Thanks.
@ilia3367 Finally Rooted. Thank you so much for your work. Very appreciate!
Tuandroidaldia said:
Nope, it's not working on Motorola One Action, it says: "<bootloader> validation image failed" using my Magisk Patched Boot.img. Did you patched your boot using another tool or how?
Thanks.
Click to expand...
Click to collapse
what about vbmeta? was possible to flash it?
@ilia3367 before Root and after unlock the bootloader when I touched the system update option, it said: "system integrity is compromised" now after Root when i touch it , it check for update again. It means that I can update the firmware via ota?
AndresOrue said:
@ilia3367 before Root and after unlock the bootloader when I touched the system update option, it said: "system integrity is compromised" now after Root when i touch it , it check for update again. It means that I can update the firmware via ota?
Click to expand...
Click to collapse
Magisk probably hides the bootloader status so that update check works, but it will most likely fail during install. At least that's how it works on moto one and moto one power.
On moto one I either reflash current build without wipe and then take ota and re-root after, or just flash the update if I get them early, and re-root-
AndresOrue said:
It means that I can update the firmware via ota?
Click to expand...
Click to collapse
I don't think it's possible. The system must be completely virgin to update the OTA. Then why do I need a Root? I need it to customize the system.
ilia3367 said:
I don't think it's possible. The system must be completely virgin to update the OTA. Then why do I need a Root? I need it to customize the system.
Click to expand...
Click to collapse
Thanks a lot. I just unlocked my BL for the second time and this root method is working fine.
May I ask if you just used magisk manager to patch boot, cause when I do I get error on flash.
Code:
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (33792 KB) OKAY [ 1.172s]
Writing 'boot_a' FAILED (Status read failed (Too many links))
And how did you patch vbmeta?
I'm just curious since this patched boot isn't the latest and I wonder how to make this work with the latest boot.img from September patch update.
So after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root ; i modified the contents so it would fit the moto phone a bit better:, but thnx goes to Ibolito over at the pixel 3 forums
1 ) Download the latest Android factory image for your device ("see this guide on where to find it.
2 ) Extract the "boot.img" file from the downloaded image and copy it to your phone.
Warning! Make absolutely sure the firmware is exactly the same as the installed one. If not, you might loose touch.
Be aware that LMSA will download the latest firmware, even if it is not yet installed. That might break your touchscreen
Click to expand...
Click to collapse
3 ) Download latest Magisk Manager application on your phone and install it :
Link
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched.img
edit: i received a comment that the name might be something like Magisk_patched_somerandomletters_.img since the latest magisk update
5 ) Enable adb debugging on your phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
extra: You could test a single boot with that image by typing "fastboot boot magisk_patched.img"
if it boots fine you should have root for this single boot / magisk would show as installed.
9 ) When it's done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and check if everything is good, and it should be
extra info:
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Edit: rewritten entire post so it would look more like a guide, and extra warning because a lot of people seem to loose touch if they don't have the exact same firmware downloaded as on their phone.
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
testtubebaby said:
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
Click to expand...
Click to collapse
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
pjottrr said:
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
Click to expand...
Click to collapse
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Sorry, no idea, i found the provided link via google,
testtubebaby said:
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
zuggi_m said:
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
Click to expand...
Click to collapse
@zuggi_m , how does posting the same url help?
i don't see a retgb here ....
Maybe someone with more dev experience can tell if you need the exact same firmware or if the version numbers are the same it is ok to use that file ?
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
mingkee said:
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
Click to expand...
Click to collapse
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
pjottrr said:
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
Click to expand...
Click to collapse
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
mingkee said:
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
Click to expand...
Click to collapse
maybe i'm missing your point here, my description is just so people who have to figure it out can just use my steps to get root, it is indeed based on fastboot flashing . so i'm not sure what you are trying to say, or am i misinterpreting something?
https://forum.xda-developers.com/motorola-one-hyper/development/rom-omnirom-t4044405
I did root on One Hyper (shipped with Android 10) using fastbootd method
Used old method soft brick my One Hyper
That's why I'd like to know
pjottrr said:
so after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root
you need to download the firmware for our device,
That can be found here;
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETEU/
after that, extract, patch, fastboot install patched version, done.
I did have some issues with the current magisk manager ( from highonandroid, i did find another source, installed version 7.5.1 of the magisk manager from this source
and that one was able to patch the boot.img
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Click to expand...
Click to collapse
There's a head up
US version: Sofia
The rest: Sofiar
I will buy US G Power in May and let's the fun begin
Check out One Hyper general to install Dolby Atmos and it can be toggle on/off.
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
CCivale said:
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
Click to expand...
Click to collapse
So you should know G Stylus ROM is Sofiap.
Be aware the way Android 10 flashing is different.
Download and install the latest ADB in order to access fastbootd (fastboot reboot fastboot) and flash boot, recovery, dtbo, vbmeta, and super
Hmmmm, I will have to read more about fastbootd in your other thread.
I did use the boot.img for the sofiap.
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
hazd said:
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
Click to expand...
Click to collapse
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
pjottrr said:
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
rsdsecure-cloud.motorola.com/download/SOFIA_RETAIL_QPM30.80-51_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
hazd said:
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
Click to expand...
Click to collapse
I downloaded the kernel and waiting for the unit.
I can flash full ROM with fastboot and fastbootd, but just flashing kernel would be much faster.
Moreover, check One Hyper general to get Dolby Atmos because you can turn on and off anytime you want.