Fresh off the oven. Seeing all kinds of reports. Working, boot loops, etc.
Proceed with caution, ALWAYS BACKUP and download the uninstaller just in case anything goes wrong. And, of course, post your results here!
Be aware that Xposed is also available as a Magisk module and that we don't know yet if this works on our device (either Magisk or normal installation)
Magisk thread with links to APK and ZIP for systemless installation.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
News:
https://www.xda-developers.com/official-xposed-framework-android-nougat/
Here I am having infinite boot. I just gave up trying to install.
---------- Post added at 01:42 PM ---------- Previous post was at 01:25 PM ----------
Navegante13 said:
Here I am having infinite boot. I just gave up trying to install.
Click to expand...
Click to collapse
I already managed to install. The problem was that the first boot after installation takes a while.
You installed the magisk module or the regular zip?
My Magisk installation fails with a .img mount error....
Navegante13 said:
Here I am having infinite boot. I just gave up trying to install.
---------- Post added at 01:42 PM ---------- Previous post was at 01:25 PM ----------
I already managed to install. The problem was that the first boot after installation takes a while.
Click to expand...
Click to collapse
You installed the magisk module or the regular zip?
My Magisk installation fails with a .img mount error....
This is working for me. I downloaded the newest version of the xposed installer app (3.1.2). i clicked the 81.1 version of xposed to install. i chose to install from within the app. i rebooted and waited and it was successful.
Navegante13 said:
Here I am having infinite boot. I just gave up trying to install.
---------- Post added at 01:42 PM ---------- Previous post was at 01:25 PM ----------
I already managed to install. The problem was that the first boot after installation takes a while.
Click to expand...
Click to collapse
sirkuttin said:
This is working for me. I downloaded the newest version of the xposed installer app (3.1.2). i clicked the 81.1 version of xposed to install. i chose to install from within the app. i rebooted and waited and it was successful.
Click to expand...
Click to collapse
I can confirm this exact procedure worked for me. Download Xposed Manager App (newest version), from there version 88.1, flashed and after a 5 min boot, worked flawlessly.
sirkuttin said:
This is working for me. I downloaded the newest version of the xposed installer app (3.1.2). i clicked the 81.1 version of xposed to install. i chose to install from within the app. i rebooted and waited and it was successful.
Click to expand...
Click to collapse
Confirmed, thanks!
I got magisk installed but I'm using their "core mode", AKA it's just the super user.
Xposed is working fine but I did notice some performance changes
Related
Made a couple of scripts for people who are having problems moving between the beta and any CM13 compatible rom (and vice versa).
Firstly, they are both zip files but NOT FLASHABLE FILES.
Just unpack either one, go into the folder and run the rescue.bat file as admin (right click and choose "run as administrator") while you have your OP2 in fastboot mode (Windows only, anyone wanting to convert them, feel free )
All it does is flashes all the partitions from the OOS3 beta one by one and then flashes the compatible TWRP version at the end or flashes the CM13 compatible partitions and the latest TWRP (3.0.1.0 for now) at the end.
**MAKE SURE YOU HAVE COPIED THE BETA ZIP FILE ON TO YOUR PHONE FIRST OR A CM13 COMPATIBLE ROM (WITH GAPPS PACKAGE) **
Hold down your volume down key once the script is done and it'll reboot into the compatible recovery, once you wipe your system, data and cache partitions in there and flash the rom you should be good to go. Just make sure when you restart from TWRP you choose to disable the "stock recovery replacement"
To go from any rom to the OOS 3 Beta use this pack:
https://www.androidfilehost.com/?fid=24459283995310520
To go from the OOS 3 Beta to CM13 compatible use this pack (Updated with TWRP 3.0.1.0) :
https://www.androidfilehost.com/?fid=24459283995311240
Any problems after using either one post below but please DON'T FORGET TO HAVE YOUR NEW ROM READY TO GO ON THE STORAGE FOR AFTER THE SCRIPT.
djsubterrain said:
Made a couple of scripts for people who are having problems moving between the beta and any CM13 compatible rom (and vice versa).
Firstly, they are both zip files but NOT A FLASHABLE FILES.
Just unpack either one, go into the folder and run the rescue.bat file as admin (right click and choose "run as administrator") while you have your OP2 in fastboot mode (Windows only, anyone wanting to convert them, feel free )
All it does is flashes all the partitions from the OOS3 beta one by one and then flashes the compatible TWRP version at the end or flashes the CM13 compatible partitions and the latest TWRP (3.0.0.2 for now) at the end.
**MAKE SURE YOU HAVE COPIED THE BETA ZIP FILE ON TO YOUR PHONE FIRST OR A CM13 COMPATIBLE ROM (WITH GAPPS PACKAGE) **
Hold down your volume down key once the script is done and it'll reboot into the compatible recovery, once you wipe your system, data and cache partitions in there and flash the rom you should be good to go. Just make sure when you restart from TWRP you choose to disable the "stock recovery replacement"
To go from any rom to the OOS 3 Beta use this pack:
https://www.androidfilehost.com/?fid=24459283995310520
To go from the OOS 3 Beta to CM13 compatible use this pack:
https://www.androidfilehost.com/?fid=24459283995310560
Any problems after using either one post below but please DON'T FORGET TO HAVE YOUR NEW ROM READY TO GO ON THE STORAGE FOR AFTER THE SCRIPT.
Click to expand...
Click to collapse
Tried it but didn't work. The recovery remains the same een after adb shows its flashed in fastboot mode... maybe I should try unlocking the OEM again as I just flashed 3.0 beta and think it might have locked OEM
indroider said:
Tried it but didn't work. The recovery remains the same een after adb shows its flashed in fastboot mode... maybe I should try unlocking the OEM again as I just flashed 3.0 beta and think it might have locked OEM
Click to expand...
Click to collapse
Which way were you trying to go? From CM13 to 3.0 Beta or the other way round? Also did you run your command window or the script with administrator privileges?
Just updated the CM13 Rescue script to include the newly released TWRP 3.0.1.0:
https://www.androidfilehost.com/?fid=24459283995311240
indroider said:
Windows only, anyone wanting to convert them, feel free
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=66166823&postcount=7
gonna bookmark this x)
Go to OxygenOS 3.0 -> https://mega.nz/#!0xxWEAzR!jv4I-FzULD7l0tNWPsIq3Im6w91YZ1hVVuFmv6h55TA
Go back to CM13 -> https://mega.nz/#!R5oFBb6D!tzSYYafx8Uqm-ToJrU3YlHOZQ93_EQyjH5ibM_50Yxk
Disclaimer:
By using this script YOU will take full responsibility for any damage to your device!
Hardware or software! no one forcing you to use it.
So please do not blame me if you read wrong! or didn't read at all the instructions that i have written for YOU.
Will update after work with new TWRP 3.0.2.0...
Here you got I have updated the recovery in the cm13 resuce for you. Its all your work... Thank you.. Here is the link
https://mega.nz/#!LARRCTiZ
---------- Post added at 08:11 PM ---------- Previous post was at 08:03 PM ----------
First thanks for the scripts!
I tried today to get back go from OOS3 to CM13 but I now have a Chinese TWRP. Can anybody tell me how to change that back to English?! My Chinese is not really existing
Found the menue entry by testing. In case anybody else gets that problem:
- in the main menu click the 3rd button on the right
- on the top menu click the globe icon
- now you can change the language
guys , can someone share the steps for going back to CM13 to OSS 3.0
---------- Post added at 05:05 PM ---------- Previous post was at 05:05 PM ----------
I tried the process but not working for Switching from OSS 3.0 to CM13.
Please help
---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------
indroider said:
Here you got I have updated the recovery in the cm13 resuce for you. Its all your work... Thank you.. Here is the link
https://mega.nz/#!LARRCTiZ
Click to expand...
Click to collapse
Hey.. Can you please share the key for decryption ?
hcbhatt said:
guys , can someone share the steps for going back to CM13 to OSS 3.0
---------- Post added at 05:05 PM ---------- Previous post was at 05:05 PM ----------
I tried the process but not working for Switching from OSS 3.0 to CM13.
Please help
---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------
Hey.. Can you please share the key for decryption ?
Click to expand...
Click to collapse
Try this link
https://mega.nz/#!LARRCTiZ!rfjvwOIYO1v_FhKQ-CA0yDZcm33Lg5lUM_4TtWUwBgU
also u just need to extract the zip and reboot your phone into fastboot mode and the connect the mobile and open the folder where you extracted and run rescure.bat [ please do not run as admin ]
It will flash the partitions for the CM based roms and you can then reboot in recovery when the command prompt ask you to hold the down arrow key and press any key and now the trwp 3.0.2 will open and just wipe the data, system and cache and dalvik and then flash the cm and gapps you will be good to go after the reboot
Does anyone know why OP2 roms are based off two different firmwares?
indroider said:
Try this link
https://mega.nz/#!LARRCTiZ!rfjvwOIYO1v_FhKQ-CA0yDZcm33Lg5lUM_4TtWUwBgU
also u just need to extract the zip and reboot your phone into fastboot mode and the connect the mobile and open the folder where you extracted and run rescure.bat [ please do not run as admin ]
It will flash the partitions for the CM based roms and you can then reboot in recovery when the command prompt ask you to hold the down arrow key and press any key and now the trwp 3.0.2 will open and just wipe the data, system and cache and dalvik and then flash the cm and gapps you will be good to go after the reboot
Click to expand...
Click to collapse
Thanks indroider
Sent from my ONE A2003 using XDA-Developers mobile app
[/COLOR]
knpk13 said:
Does anyone know why OP2 roms are based off two different firmwares?
Click to expand...
Click to collapse
he roms are not based on different firmware the main diff with MM stock n other roms is the partion table and this is a general scenario for many mobiles
---------- Post added at 11:32 PM ---------- Previous post was at 11:26 PM ----------
hcbhatt said:
Thanks indroider
Sent from my ONE A2003 using XDA-Developers mobile app
Click to expand...
Click to collapse
Your most welcome. Is your issue resolved? Hit thanks if you wish ..
Alright guys here's the situation:
I'm really new to this and I've screwed up.
I was using TWRP to perform a factory reset and I made an advanced wipe and wiped the following partitions:
-Dalvik/ART Cache
-Cache
-Data
-Internal Storage
-Vendor
After the wipe was done I was unable to boot into android,the phone kept trying to reboot.
Now whenever i try to start up my phone:
I first get the default huawei animation for turning it on
Then i get the disclaimer saying how the phone was opened and it isn't secure anymore(ever since it got rooted)
Then the phone tries to boot and it goes back to the black screen.
What should I do to restore my system again?
Or maybe i need to reinstall it completely?
TL;DR How do i reflash my p10 lite with the stock ROM?
UPDATE:Trying to boot into the bootloader through twrp>reboot gets me into the rescue mode screen.
Justkill43 said:
UPDATE:Trying to boot into the bootloader through twrp>reboot gets me into the rescue mode screen.
Click to expand...
Click to collapse
You should flash Oeminfo again.
---------- Post added at 11:25 PM ---------- Previous post was at 11:24 PM ----------
maartenw8 said:
You should flash Oeminfo again.
Click to expand...
Click to collapse
Also check if there is a vendor IMG in your stock rom. If so, flash the correct one
maartenw8 said:
You should flash Oeminfo again.
---------- Post added at 11:25 PM ---------- Previous post was at 11:24 PM ----------
Also check if there is a vendor IMG in your stock rom. If so, flash the correct one
Click to expand...
Click to collapse
So how would I go about that?
Just use TWRP to install the imgs?
Also where would could I find a ROM?I'm an idiot that didn't back it up,because I'm hasty.
Justkill43 said:
So how would I go about that?
Just use TWRP to install the imgs?
Also where would could I find a ROM?I'm an idiot that didn't back it up,because I'm hasty.
Click to expand...
Click to collapse
Yes use TWRP and search the rom for your model on xda or Google or so I don't have the p10 lite so I can't help you there..
THIS POST IS EXTENSION TO
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502
Please read carefully and flash kernel for the LATEST UPDATE (Project SUZU )
34.3.A.0.244 - 7.1.1 - 09 NOV 2017 update
F5122 IS AT https://mega.nz/#F!DEQykYjL!Vux2m1_Rug9hg9B4_q0ifw
F5121 .. https://mega.nz/#F!CBhRyR7Z!L5uo_GWiCzXcNWQaZGJ9bQ (THANKs @eagleeyetom )
both f5121/5122 folders have 1 kernel image,
FLASH THE ROM
FLASH THE KERNEL,
FLASH TWRP,
BOOT IN TO TWRP .
FLASH MAGISK or SUPERSU, VIA FLASHABLE ZIP
BOOT THE DEVICE
IF YOU HAVE FLASHED MAGIK THEN INSTALL MAGIS MANAGER
MAGISK POST https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
CHAINFIRE SUPERSU ZIPs LATEST AT https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
-if you don't have th 34.3 fsc script , i have included in the folder (closing Partitions takes TIME, so be Patient ! )
-also i have inclused mixer_paths_wcd9335.xml, on 98% VOLUME level, IF you think sound output is LOW,,, just REPLACE it from /system/etc folder!
-
.
Click to expand...
Click to collapse
PREVIOUS KERNELS
for F5122_34.3.A.0.238 - 7.1.1 - 2 OCTOBER 2017 update
https://forum.xda-developers.com/xperia-x/development/rooted-kernels-f5121-f5122-34-3-0-238-t3683968
for F5122_34.3.A.0.224 - 7.1.1 - 8 SEPTEMBER 2017 update
https://forum.xda-developers.com/xp...ted-kernels-f5121-f5122-34-3-0-224-8-t3669793
for F5122_34.3.A.0.217 - 7.1.1 - 8Aug2017 update
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5121-f5122-34-3-0-217-7-t3654368
for F5122_34.3.A.0.206 - 7.1.1 - july2017 update
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f512234-3-0-206-7-1-1-t3635595
Hi,
Thx for this new update but i dont found the kernel in the package.
I found the img.clean, twrp, fsc, sr5 and magisk but no kernel..
So what can i do for F5121!?
Siggi
siggi77 said:
Hi,
Thx for this new update but i dont found the kernel in the package.
I found the img.clean, twrp, fsc, sr5 and magisk but no kernel..
So what can i do for F5121!?
Siggi
Click to expand...
Click to collapse
on https://mega.nz/#F!CBhRyR7Z!L5uo_GWiCzXcNWQaZGJ9bQ
the F5121_34.3.A.0.244_su.img is the kernel
just flash and your device will wakup ROOTED.
twrp 3.1.1 problem
on my 64 GB xperia X F5122
1. after flashing ROM if
2. I flash twrp 3.1.1 it will
3. make my system partition 40GB and i get only 20gb workable
I tried many things but flashing recovery via adb always create this problem and if i BOOT the device before going in to the partition , sony stockrom makes internal storage encrypted which then twrp3.1.1 is unable to read
plz help
@serajr @shoey63 @munjeni
Hi,
Ok thx this package is complete...
Great
Siggi
---------- Post added at 09:37 PM ---------- Previous post was at 09:33 PM ----------
Hi,
OK this file is not a .img:
F5121_34.3.A.0.244_su is the kernel but isn´t a .img
Please make a new package
Siggi
---------- Post added at 10:22 PM ---------- Previous post was at 09:37 PM ----------
In the package for F5122 is the corret .img, but for F5121 not or is the same?
siggi77 said:
Hi,
Ok thx this package is complete...
Great
Siggi
---------- Post added at 09:37 PM ---------- Previous post was at 09:33 PM ----------
Hi,
OK this file is not a .img:
F5121_34.3.A.0.244_su is the kernel but isn´t a .img
Please make a new package
Siggi
---------- Post added at 10:22 PM ---------- Previous post was at 09:37 PM ----------
In the package for F5122 is the corret .img, but for F5121 not or is the same?
Click to expand...
Click to collapse
i am sorry,
i have fixed it
please check again
thank you
Hi, great
thx for the new package
Siggi
clean kernel image is drm fixed??
kloroform said:
clean kernel image is drm fixed??
Click to expand...
Click to collapse
yes sir, it is,
That is little bit complicated we need a good guide
---------- Post added at 02:56 PM ---------- Previous post was at 02:31 PM ----------
I flashed rom>kernel with su then flashed twrp.
Later I flashed the magisk.zip and reboot the system but everytime its entering the twrp screen.
Wont going bootanimation and starts the phone. Just twrp screen.
OH GOD I SOLVED THIS. HERE MY SOLUTION:
First things first, I WANT TO FLASH MAGISK AND NO MORE USE SUPERSU, THATS I WANT. IF YOU WANT TO USE MAGISK HERE IS MY SOLUTION.
1. Flash the stock rom on the post. (up)
2. When flash finished, boot the phone and close the phone.
3. Flash the clean kernel with flashtool.
4. Boot the phone, is everything okay, close again.
5.a So there is little bit strange, open adb on windows (yes really. dont use flashtool this time)
5.b Flash the twrp-3.1.1-suzu-2017.07.16.img from this address: https://androidfilehost.com/?w=files&flid=197369 (on the middle)
5.c the command is here "fastboot flash recovery twrp-blablabla.img"
6. and type "fastboot reboot" will boot up your phone.
7. If its really open, -not stuck at the sony logo or everytime goin in twrp- you did! congrats!
I hope it help you
xxarigattoxx said:
That is little bit complicated we need a good guide
---------- Post added at 02:56 PM ---------- Previous post was at 02:31 PM ----------
I flashed rom>kernel with su then flashed twrp.
Later I flashed the magisk.zip and reboot the system but everytime its entering the twrp screen.
Wont going bootanimation and starts the phone. Just twrp screen.
OH GOD I SOLVED THIS. HERE MY SOLUTION:
First things first, I WANT TO FLASH MAGISK AND NO MORE USE SUPERSU, THATS I WANT. IF YOU WANT TO USE MAGISK HERE IS MY SOLUTION.
1. Flash the stock rom on the post. (up)
2. When flash finished, boot the phone and close the phone.
3. Flash the clean kernel with flashtool.
4. Boot the phone, is everything okay, close again.
5.a So there is little bit strange, open adb on windows (yes really. dont use flashtool this time)
5.b Flash the twrp-3.1.1-suzu-2017.07.16.img from this address: https://androidfilehost.com/?w=files&flid=197369 (on the middle)
5.c the command is here "fastboot flash recovery twrp-blablabla.img"
6. and type "fastboot reboot" will boot up your phone.
7. If its really open, -not stuck at the sony logo or everytime goin in twrp- you did! congrats!
I hope it help you
Click to expand...
Click to collapse
the guide is here
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502
also twrp3.1.1 works best at 32gb variant by giving 20gb workable and putting systemparittion to 12gb
however it does the SAME with 46gb variant and give only 20gb workable and put system partition 40 gb
thats why for 64gb variants i don't recomend using twrp3.1.1
Hi, when you say flash the rom you mean in Flashtool ? There is no twrp flashable rom here ?
Jomoteck said:
Hi, when you say flash the rom you mean in Flashtool ? There is no twrp flashable rom here ?
Click to expand...
Click to collapse
once you flash the modified kernel with supersu then there is no need for twrp, simply boot your device and it will wakeup rooted.
however if you wana use magisk and your device is 64gb then i highly recommend you to do this
1. flash rom
2. flash the modified kernel
3. boot the device and go thru sony setup , give google account and let it sync
4. switch off mobile after 15 or so mins
5. flash twrp3.1.1 suzu (given in the mega link, in the OT)
6. HOLD power and VOLUME DOWN BUTTON till PINK led comes on sonylogo and you are taken to twrp, keep system readonly and flash magisk ( via otg or if you had it in your sd card prior) ( at this point you may flash other zips also, if there are any)
7. twrp may give you error such as... cannot mount internal storage etc, just ignore.
8. after flashing, switchoff mobile, and boot it into system.
9. for safty purposes, you can erase twrp by connecting device in fastboot mode and executing following command
Code:
fastboot erase recovery
now you can ask me why i let you boot your device first. normally its unprecedented.
the reason i explain here
https://forum.xda-developers.com/showpost.php?p=74573987&postcount=121
hello
i have 34.3.A.0.217 rom with root. how can i update 34.3.A.0.244 ? can you help me anyone ?
nova001 said:
hello
i have 34.3.A.0.217 rom with root. how can i update 34.3.A.0.244 ? can you help me anyone ?
Click to expand...
Click to collapse
1. download 34.3.A.0.244 using xperifirm under flashtool
2. flash it using flashtool (please google the tutorial ) (wipe everything while flashing
**** TAKE BACKUP of EVERYTHING (DATA) ****
YasuHamed said:
1. download 34.3.A.0.244 using xperifirm under flashtool
2. flash it using flashtool (please google the tutorial ) (wipe everything while flashing
**** TAKE BACKUP of EVERYTHING (DATA) ****
Click to expand...
Click to collapse
thats oke, but we cant dowload anywhere? only xperifirm ?
nova001 said:
thats oke, but we cant dowload anywhere? only xperifirm ?
Click to expand...
Click to collapse
Xperifirm is the best
Other servers i cant guarantee
I was able to flash rom, flash kernel, flash root and boot the phone and was able to use it.
PROBLEM:
- It heats up during use.(FIXED) constant mobile data was the cause..
- Everytime I lock the screen my mobile data turns on when I unlock the SCREEN. (FIXED) disable find my device as administrator.
HI question does FCS_thermal_Xperia_X_v1.3.zip work for Nougat?
cyanides13 said:
HI question does FCS_thermal_Xperia_X_v1.3.zip work for Nougat?
Click to expand...
Click to collapse
Yes it works I use it actually.
Hi guys I was able to root my P10 using magisk and the new treble project on oreo very easily.
All credit goes to @topjohnwu as he's the creator of Magisk and this method all i'm doing is sharing his work and adding the boot image for the P10
Requirements:
Your PC
P10 ON OREO B360 (this only works on oreo if you try to do it on nougat you could easely brick your device)
Bootloader Unlocked (?)
ADB & Fastboot
I actually don't know if you need to have your bootloader unlocked as it's using the treble project to update the boot partition.
I had mine unlocked when i did this.
Step 1:
Get your boot image from update files (huawei update extractor > settings > uncheck the first 3 checkboxes) here i have the boot image from my VTR-L29C432B360
Install the latest Magisk Manager apk from here.
Step 2:
Open Magisk Manager, go to Settings > Update Channel > Custom Update channel with this link http://goo.gl/jefZKH
after that check if the latest magisk update is v15.4 (as the time of posting this guide)
if it says Invalid Update Channel you probably misspelled the link
Step 3:
Copy your boot image to your internal storage/sd card
Go on Magisk Manager > Install > Patch boot image file > Select the boot image on your internal storage/sd card
when it finishes go on your pc and pull the patched boot image to your desktop or desired folder. it will be stored on your internal memory/MagiskManager/patched-boot.img
Step 4:
Open cmd on the same folder as your patched boot image
Go to fastboot (Power-off then Vol+ and Power)
now on cmd type
Code:
fastboot devices
should come as response a serial number and fastboot
this means your device is connected to you pc and on fastboot
after that type
Code:
fastboot flash ramdisk patched_boot.img
it will flash the patched boot image
when it's done just reboot
and you're set!!
You'll have root with Magisk and pass safety net without a problem.
Friend, thanks for the information. Sorry you know how to install viper4android in B360
DarkPJV said:
Friend, thanks for the information. Sorry you know how to install viper4android in B360
Click to expand...
Click to collapse
i wish i knew... i'm also looking for how to install it. if i get it to work i'll post a guide too
D4XT3R said:
i wish i knew... i'm also looking for how to install it. if i get it to work i'll post a guide too
Click to expand...
Click to collapse
It would be fantastic.friend
Thank you very much for this guide, worked like a charm.
I even have full SafetyNet back, incl. CTS. What I didn't have before I flashed the patched bootimage.
I'm just wondering why you suggest to modify the update channel? I got an error message anyway (and I didn't misspell it), so I changed it back to 'Stable' and had not problems.
smashedup said:
Thank you very much for this guide, worked like a charm.
I even have full SafetyNet back, incl. CTS. What I didn't have before I flashed the patched bootimage.
I'm just wondering why you suggest to modify the update channel? I got an error message anyway (and I didn't misspell it), so I changed it back to 'Stable' and had not problems.
Click to expand...
Click to collapse
well the modified channel update is one that @topjohnwu modified for huawei's treble enabled phones like the P10 so that we wouldn't have any problem with safety net or flashing the boot partition but if it worked for you it might work for others too
Hello i just upgraded from nougat to oreo and bootloader is locked again i tried to flash the recovery img without success any solution to root that phone?
samy0x said:
Hello i just upgraded from nougat to oreo and bootloader is locked again i tried to flash the recovery img without success any solution to root that phone?
Click to expand...
Click to collapse
do you have oem unlocking enabled on your phone? if after enabling this option it still fails to flash the patched boot image unlock the boot loader, I know a pain in the ass, but you'll pass safety net without a problem
D4XT3R said:
do you have oem unlocking enabled on your phone? if after enabling this option it still fails to flash the patched boot image unlock the boot loader, I know a pain in the ass, but you'll pass safety net without a problem
Click to expand...
Click to collapse
Yes
Phone Locked
FRP Unlock
have you tried it again and worked? if not it only works with unlocked bootloader
D4XT3R said:
have you tried it again and worked? if not it only works with unlocked bootloader
Click to expand...
Click to collapse
Yes i tried again no solution i'll wait for sometime if no solution i'll unlock bootloader
I'm exploring that solution maybe : https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-root-preserve-user-data-t3716547
I can confirm that Magisk v16 works for me on VTR-L29C432B360. Installed with the Magisk Manager without flashing in TWRP.
Jannomag said:
I can confirm that Magisk v16 works for me on VTR-L29C432B360. Installed with the Magisk Manager without flashing in TWRP.
Click to expand...
Click to collapse
How did you do that
samy0x said:
How did you do that
Click to expand...
Click to collapse
I opened the Magisk Manager app and it prompted me that v16 is available for install. Then I pressed "Install", rebooted and that was it.
What about working Xposed and Magisk like on Nouget EMUI 5.1? I'm always stock in boot-look when i try to flash BETA3 Xposed v90 SDK 26 amr64
---------- Post added at 07:59 PM ---------- Previous post was at 07:58 PM ----------
Jannomag said:
I opened the Magisk Manager app and it prompted me that v16 is available for install. Then I pressed "Install", rebooted and that was it.
Click to expand...
Click to collapse
Yes me to, but first you need 15.4 magisk version and than you can update to v16 in MagiskManager app
urbanboymne said:
What about working Xposed and Magisk like on Nouget EMUI 5.1? I'm always stock in boot-look when i try to flash BETA3 Xposed v90 SDK 26 amr64
---------- Post added at 07:59 PM ---------- Previous post was at 07:58 PM ----------
Yes me to, but first you need 15.4 magisk version and than you can update to v16 in MagiskManager app
Click to expand...
Click to collapse
Oh, of course. Sorry, I meant with "not flashing with TWRP" that I didn't need to flash the zip for v16 manually, just install it within the app. But of course you need to install 15.4 first.
meh , cant extract ramdisk.img from update.zip...
About magisk...is the root gone away finally fixed ?
on my old nova plus,when rooted whit magisk,we had to flash that darn patched boot img every 1-2 weeks in order to re have root again
is that finally fixed ?
Jannomag said:
I can confirm that Magisk v16 works for me on VTR-L29C432B360. Installed with the Magisk Manager without flashing in TWRP.
Click to expand...
Click to collapse
Exactly the same for me... and passes safety net
---------- Post added at 02:04 PM ---------- Previous post was at 01:57 PM ----------
Can we flash TWRP 3.1.1 after rooting with Magisk ?
Big thankyou it worked like a charm
Hello. I decided to switch to CarbonROM on my Poco f1 thinking that it was based on Android 10 (I really like gesture navigation). After reformatting my device I flashed the firmware, carbonrom and then my microG package. After a little hitch with the wrong firmware it worked. Then, after realising that it didn't have android 10 gesture navigation I thought I'd switch to another ROM. I booted to my recovery (SkyHawk recovery, based on twrp) and went to re format my device. The recovery asked me for a password to decrypt my device (which I found odd as I had never set up a password on CarbonROM) which I cancelled the request and went to reformat my device. I typed in yes and it told me the "Unable to mount storage". Wiping, mounting or any other action yields the same response. I tried rebooting to system and after the CarbonROM boot animation it told me "Encryption unsuccesful" and some text saying I need to reset my phone. I pushed the reset phone button and after a pop up claims to reset it, it boots back to recovery. The main console in the recovery says "cryptkeeper.showFactoryReset() corrupt=false". I have repeated multiple times. All I can access is the recovery (from which I can do nothing) and fastboot.
Is my phone stuffed or can I restore it somehow?
Flash twrp recovery.
Adidas108 said:
Flash twrp recovery.
Click to expand...
Click to collapse
How though? Despite failing earlier, I have now been able to boot up into CarbonROM (so my phone is not bricked ) but I am unable to wipe / reformat my phone from SkyHawk. I know that you can flash a recovery if you have Magisk root, but even flashing Magisk doesn't work from SkyHawk. Can I get TWRP to replace SkyHawk through Fastboot / ADB or anything like that?
Just flash twrp img file using shrp then boot to recovery
---------- Post added at 07:08 AM ---------- Previous post was at 07:05 AM ----------
Use this one
MOD EDIT: Link Removed
---------- Post added at 07:10 AM ---------- Previous post was at 07:08 AM ----------
You can use fastboot
Adidas108 said:
Just flash twrp img file using shrp then boot to recovery
---------- Post added at 07:08 AM ---------- Previous post was at 07:05 AM ----------
Use this one
---------- Post added at 07:10 AM ---------- Previous post was at 07:08 AM ----------
[/COLOR]You can use fastboot
Click to expand...
Click to collapse
Would mind linking me to instructions on how to do with fastboot?
Thank you
hslav said:
Would mind linking me to instructions on how to do with fastboot?
Thank you
Click to expand...
Click to collapse
Nevermind I got it working. Thank you!
hslav said:
Nevermind I got it working. Thank you!
Click to expand...
Click to collapse
Good to hear.
For others check link bellow about adb/fastboot
https://www.youtube.com/redirect?ev...-adb-fastboot-installer-tool-windows-t3999445