IMPORTANT
I havent made this rom and im not responsible of any problem with it. Its just a tutorial.
The best Gsi fully working, Blissos Rom (unnoficial) on N20U Snapdragon:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Full credits to Nazim, autor of this GSI rom
ABOUT
An open-source operating system based on Android with customizations, options and added security features.
LINKS
Telegram: https://t.me/naz_dev/46
Download: https://sourceforge.net/projects/gsi-projects/files/v402.1/BlissOS-15.3/
WHAT WORKS
Almost everything is working:
NFC
FINGERPRINT
SPEN
BLUETOOTH
RIL
CAMERA (not the best quality)
ETC...
WHAT NOT WORKS
LOCATION
Anything else report it
INSTRUCTIONS
1. Unlocked Bootloader
2. TWRP installed (https://forum.xda-developers.com/t/...r-galaxy-note-20-ultra-5g-snapdragon.4210985/)
3. Once you have the TWRP installed, you need to donwload the GSI, extract the .img file and transfer it to the phone via TWRP connection.
4. Flash the image file on system.
5. Wipe factory reset.
6. Reboot.
7. Setting up your phone, I recommend you to skip the security (fingerprint and pin), and VERY IMPORTANT, skip the google log in account.
8. Once you are ready, go to settings > apps > google play services > uninstall upgrades.
9. Log in google and READY!.
10. I recommend you to go to PHH settings, force fps to 96hz and then to 120hz. On samsung settings, enable extended brightness. To enable Bluetooth, go to misc settings, then activate "Force-disable A2DP offload".
11. Now you can add security methods, including fingerprint.
ENJOY!
its important to mention that other GSI roms work well: PHH AOSP, Pixel Experience (problem with 120hz), OctaviOS. All of them have little important problems (battery, ril...), and its important to remark that the battery life is AMAZING in this rom (between 8-9h with half birghtness and bluetooth).
HOPE WILL HELP TO EVERYONE TIRED OF ONE UI
IF ANYONE CAN HELP WITH ROOT, CAMERA (PORT SAMSUNG ONE) AND LOCATION IT WOULD BE AMAZING
This is amazing, when I get tired of stock one ui, will definitely try this
CRDROID
is also working amazing, its a newer release, its more smooth but there is a problem with the fingerprint and safetynet (im not able to pass it). Location problem solved and its performing a little better in general
Link: https://sourceforge.net/projects/gsi-projects/files/v411/crDroid-8.3/
FerJavi said:
CRDROID
is also working amazing, its a newer release, its more smooth but there is a problem with the fingerprint and safetynet (im not able to pass it). Location problem solved and its performing a little better in general
Click to expand...
Click to collapse
Do you mind sharing the link to CRDROID?
Suntaina said:
Do you mind sharing the link to CRDROID?
Click to expand...
Click to collapse
Shared, edited post
I spent a few days messing with a few of these GSI builds. I'd fixed most of the problems i was having except for calls. I could not place a call nomatter what i did.
As soon as i would dial. it'd immediately hang up. Which firmware vendor.img are you guys using?
My most successful combo was Android 11 firmware with an Android 10 vendor... but still no calling.
flippage said:
I spent a few days messing with a few of these GSI builds. I'd fixed most of the problems i was having except for calls. I could not place a call nomatter what i did.
As soon as i would dial. it'd immediately hang up. Which firmware vendor.img are you guys using?
My most successful combo was Android 11 firmware with an Android 10 vendor... but still no calling.
Click to expand...
Click to collapse
Hi dude, I was able to get calls working with crdroid A12 with a12 vendor. The problem with it was safetynet, and i was unable to root gsi to get safetynet fix. After a few days using bliss os the calls stopped working (as u said).
flippage said:
I spent a few days messing with a few of these GSI builds. I'd fixed most of the problems i was having except for calls. I could not place a call nomatter what i did.
As soon as i would dial. it'd immediately hang up. Which firmware vendor.img are you guys using?
My most successful combo was Android 11 firmware with an Android 10 vendor... but still no calling.
Click to expand...
Click to collapse
Did u managed to root gsi? i tried A11 but i had a problem with landscape mode (black stripes appeared on my screen).
Maybe we can create a telegram group to share all this things
UPDATE:
I've managed to install magisk, location is also working, ril is working, ALL IS WORKING. I installed Gcam and photos are good, not amazing, but good enough.
There is a new rom, AncientOs, is the rom Im using now, but PE+ is working also amazing.
SCREENSHOOTS:
ROOT WITH MAGISK:
1. Latest Odin flashable update is required (at least this is the best worked for me).
2. Transfer the AP file to the device, and install
MAGISK
3. Go to Install, then select patch image (recommended), then select the AP file you have transfered to the phone.
4. After the process, transfer the magisk patched image to the PC, use WINRAR or 7ZIP to extract the files, IMPORTANT the file you need is only boot.img.
5. After you have done this, transfer the boot.img file to the phone, and after installing the rom, flash the boot.img file via TWRP as boot image.
6. Boot and Enjoy, root is done, pass safetynet if you need by using magisk fix.
GCAM FILES
So I'm waiting Exynos variant.
FerJavi said:
UPDATE:
I've managed to install magisk, location is also working, ril is working, ALL IS WORKING. I installed Gcam and photos are good, not amazing, but good enough.
There is a new rom, AncientOs, is the rom Im using now, but PE+ is working also amazing.
SCREENSHOOTS:
View attachment 5592089
ROOT WITH MAGISK:
1. Latest Odin flashable update is required (at least this is the best worked for me).
2. Transfer the AP file to the device, and install
MAGISK
3. Go to Install, then select patch image (recommended), then select the AP file you have transfered to the phone.
4. After the process, transfer the magisk patched image to the PC, use WINRAR or 7ZIP to extract the files, IMPORTANT the file you need is only boot.img.
5. After you have done this, transfer the boot.img file to the phone, and after installing the rom, flash the boot.img file via TWRP as boot image.
6. Boot and Enjoy, root is done, pass safetynet if you need by using magisk fix.
GCAM FILES
Click to expand...
Click to collapse
Grea job dude, when my note 20 ultra doesn’t get anymore updates, I will definitely try this or perhaps very soon lol.
Do you know if we could get esim to work? I know some dude on this forum made it work earlier, rooted on android 11, this model.
Suntaina said:
Grea job dude, when my note 20 ultra doesn’t get anymore updates, I will definitely try this or perhaps very soon lol.
Do you know if we could get esim to work? I know some dude on this forum made it work earlier, rooted on android 11, this model.
Click to expand...
Click to collapse
I´ll check it
Nettwerk said:
So I'm waiting Exynos variant.
Click to expand...
Click to collapse
At the moment, exynos chips are supported, so you only need to have TWRP (that supports flashing images, I think the one available can do it).
What is link for Exynos variant ROM?
FerJavi said:
UPDATE:
I've managed to install magisk, location is also working, ril is working, ALL IS WORKING. I installed Gcam and photos are good, not amazing, but good enough.
There is a new rom, AncientOs, is the rom Im using now, but PE+ is working also amazing.
SCREENSHOOTS:
View attachment 5592089
ROOT WITH MAGISK:
1. Latest Odin flashable update is required (at least this is the best worked for me).
2. Transfer the AP file to the device, and install
MAGISK
3. Go to Install, then select patch image (recommended), then select the AP file you have transfered to the phone.
4. After the process, transfer the magisk patched image to the PC, use WINRAR or 7ZIP to extract the files, IMPORTANT the file you need is only boot.img.
5. After you have done this, transfer the boot.img file to the phone, and after installing the rom, flash the boot.img file via TWRP as boot image.
6. Boot and Enjoy, root is done, pass safetynet if you need by using magisk fix.
GCAM FILES
Click to expand...
Click to collapse
After I extract the boot.img from inside the patched AP file and flash it i can not boot. It messes up something related to vbmeta i think. Still gonna mess with it because if it works for you I'm sure its just something I'm doing wrong.
Also, you said you have gotten calls working? When i try to place a call it immediately tells me call ended. From what i've gathered so far it's something to do with no VoLTE. I'm on AT&T which has no 3G network anymore so if that's how you're able to place calls that won't work for me.
flippage said:
After I extract the boot.img from inside the patched AP file and flash it i can not boot. It messes up something related to vbmeta i think. Still gonna mess with it because if it works for you I'm sure its just something I'm doing wrong.
Click to expand...
Click to collapse
I suposse you have flashed vbmeta disabled to flash twrp, if not, try that. Another option could be flashing vbmeta from the magisk patched AP file... Or have you tried the "multidisabler" command from twrp terminal?
Nettwerk said:
What is link for Exynos variant ROM?
Click to expand...
Click to collapse
https://sourceforge.net/projects/an...4_bgN-vndklite-Steel-20220417.img.xz/download
Try this one
FerJavi said:
I suposse you have flashed vbmeta disabled to flash twrp, if not, try that. Another option could be flashing vbmeta from the magisk patched AP file... Or have you tried the "multidisabler" command from twrp terminal?
Click to expand...
Click to collapse
Tried those and still no-go. No matter what as soon as i modify the boot.img to anything other than the original file from the firmware (FVC5) I fail to boot and get sent back into TWRP.
Link for ancient os snapdragon plz
FerJavi said:
At the moment, exynos chips are supported, so you only need to have TWRP (that supports flashing images, I think the one available can do it).
Click to expand...
Click to collapse
Can u plz give the link of ancient os for snapdragon
Are you using the vndklite version? I've been using the regular builds, I wonder if that has anything to do with my magisk issues...
Related
Unofficial release -TWRP recovery for the Galaxy J3 Emerge - SM-J327P, Qualcomm MSM8937
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Update 15/3/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.0-1_j327p_14317
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my testers @Doctur, @infixremix, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
.
Reserved
Might of bought you a pack of smokes not the beer....either way donation was just a small thankyou...its been awhike withiut root im almost forgetting why i wanted it rooted in the first place lol Enjoy the smokes or w.e the donation goes to
Ur tha sh#$ bro
Doctur said:
Might of bought you a pack of smokes not the beer....either way donation was just a small thankyou...its been awhike withiut root im almost forgetting why i wanted it rooted in the first place lol Enjoy the smokes or w.e the donation goes to
Ur tha sh#$ bro
Click to expand...
Click to collapse
Thanks for the heads up with the other member and your support. I'll report it.
@ashyx by any chance do you have this device? .. i have 7.0 J327P seen it in the Samsung kitchen but not sure if its for the Sprint or Boostmobile worst case odin wont flash it
JUSMEJOSE said:
@ashyx by any chance do you have this device? .. i have 7.0 J327P seen it in the Samsung kitchen but not sure if its for the Sprint or Boostmobile worst case odin wont flash it
Click to expand...
Click to collapse
No sorry i don't own this device.
@ashyx, forgive me for not knowing, I am not familiar all that much with the various Samsung's and pre-paid phones. I have Nexus'.
Question, the boy got a prepaid from Best Buy and it is a Samsung J327P, running 6.0.1 yet the a search on Google shows different chip, a MSM8917. So will this recovery work or not on it? Here is a picture of the about screens.
View attachment 4081849
Don't want to screw it up since I don't have original firmware to flash back to it.
PS I seen in the thread talk of a link to where you can buy a copy of the firmware for some of these could you PM me that link please?
Thank you.
Sent from my Nexus 5X using XDA-Developers Legacy app
rekids said:
@ashyx, forgive me for not knowing, I am not familiar all that much with the various Samsung's and pre-paid phones. I have Nexus'.
Question, the boy got a prepaid from Best Buy and it is a Samsung J327P, running 6.0.1 yet the a search on Google shows different chip, a MSM8917. So will this recovery work or not on it? Here is a picture of the about screens.
Don't want to screw it up since I don't have original firmware to flash back to it.
PS I seen in the thread talk of a link to where you can buy a copy of the firmware for some of these could you PM me that link please?
Thank you.
Click to expand...
Click to collapse
Yes that's the same device. MSM8917 is the same platform as MSM8937.
You have no worries.
Just post back if you get stuck and need the firmware.
Thank you so much ?, will let you know how it goes.
Sent from my Nexus 5X using XDA-Developers Legacy app
I want to try this root but I get enter pin request when I try to turn on OEM unlocking. What should I do?
joeyjojojjjjjj said:
I want to try this root but I get enter pin request when I try to turn on OEM unlocking. What should I do?
Click to expand...
Click to collapse
Pin request? Never heard of that before. Have you set a pin/password on your device?
Nevermind, my daughter pit an unlock pin on it. Got it now going to try this.
Everything went smooth! Thank you so much!
rekids said:
Everything went smooth! Thank you so much!
Click to expand...
Click to collapse
Thanks for the click, out of 141 downloaders only 3 were clickers.
I find it amsusing that the author of the thread below using stolen files from this one has just as many clicks.
https://forum.xda-developers.com/an...-j3-emerge-t3573551/post71443474#post71443474
.
No problems at all... Everything went perfect!
I flashed TWRP and everything is now force closing.. Imma try to root since that factory resets the devices (hope i already had a previous backup of everything)
Edit: Everything worked! Thank you, Dev. One question, do we disable KNOX in SuperSU?
Cyclic said:
I flashed TWRP and everything is now force closing.. Imma try to root since that factory resets the devices (hope i already had a previous backup of everything)
Edit: Everything worked! Thank you, Dev. One question, do we disable KNOX in SuperSU?
Click to expand...
Click to collapse
Yes I'd advise disabling Knox.
need help!!!!
ashyx said:
Yes that's the same device. MSM8917 is the same platform as MSM8937.
You have no worries.
Just post back if you get stuck and need the firmware.
Click to expand...
Click to collapse
Any chance you have the firmware or boot.img? after i flashed the patch all went to hell and now my phone says it has no OS
pumkinhead13 said:
Any chance you have the firmware or boot.img? after i flashed the patch all went to hell and now my phone says it has no OS
Click to expand...
Click to collapse
There's no way the patch did that. You must have wiped the system partition in twrp.
https://www.androidfilehost.com/?fid=817550096634755921
ashyx said:
There's no way the patch did that. You must have wiped the system partition in twrp.
Click to expand...
Click to collapse
uuuh no, so I did all the above said to do and everything was fine, it booted up (before i flashed the patch) then I went back into recovery, flashed the patch and selected "boot to system" it booted to samsung logo then at the top in small yellow writing just said "kernal" it sat there for 15 mins, before i pulled the battery, then flashed again....this time upon finish it stated "NO OS"
Firstly, I do not take any responsability in case anything happens to your device or your files. You decided to follow this guide at your own risk.
THIS WORKED FOR ME FOR MAGISK v14.3
ALSO WORKS ON MAGISK v14.5
I highly not recommend to use this guide for a different device other than the Xperia Z2 D6503.
All that aside, I managed to install magisk on my Stock Xperia Z2 and still keep ctsProfile and basicIntegrity: true.
HIGHLY RECOMMEND TO BACK EVERYTHING UP BEFORE PROCEEDING
You will need:
(OPTIONAL)Marshmallow FTF Firmware Here
(OPTIONAL)Flashtool Here
Magisk Manager Here
Rootkernel_v4.31_Windows_Linux.zip Here
ADB and Fastboot Here
Advanced Stock Kernel Here
TWRP Sirius Here
(OPTIONAL BUT HIGHLY RECOMMENDED) Use flashtool to flash the modified version of the stock ROM from above. It worked on this version but I can't really guarantee it will work on others. Can't really guarantee it will work on this either.(after you select the file there are 2 versions. pick the modified one).
1) Extract the Rootkernel_v4.31_Windows_Linux.zip and extract from the advanced stock kernel the boot.img (Rename it from boot.img to Old_boot.img)
2) Open cmd and use cd to reach the folder in which you extracted rootkernel.
Use the command "rootkernel Old_boot.img New_boot.img"
Say Yes to everything except installing TWRP.
3) Install Magisk Manager on your phone and copy "New_boot.img" to the phone.
4) Go to Magisk Manager settings , scroll to Update Channel and select Beta
5) Select install Magisk and select modify boot image. Select "New_boot.img" from the folder you copied it to
6) Extract adb to a folder
7) After patching the boot image at step 6, copy "patched_boot.img" from internal storage/MagiskManager to the folder in which you extracted adb
8) Copy TWRP to the adb folder and rename it to TWRP.img
9) Open cmd and use cd to navigate to the folder in which you copied adb. Type in the console "fastboot flash boot New_boot.img". Turn off your phone and then hold Volume Up whil plugging it into your pc(booting it into fastboot).
10) While still in fastboot, type "fastboot flash recovery TWRP.img"
11) Disconnect your phone from the pc. Wait a few seconds and then boot into TWRP (hold power button and Volume Down). A notification will pop up and select to "Keep System Readonly" (I think something like that). Reboot into system.
If everything worked as intended, a safetynet check will reveal everything in green, allowing you to both have root access and also run apps like Netflix and Android Pay
NOTE: Magisk Modules should be flashed via TWRP. For some reason, Magisk Manager is unable to install them.
EDIT: I tried to install xposed systemlessly but Safetynet was triggered. Don't think I can figure this out.
DahakePL tried with elite kernel and it didn't work. Writing this just in case anyone tries.
This worked for me but I can't guarantee it will work for you. (Photos at the end)
Did this guide help you? If you need any help, I will do my best to answer your questions.
I am not a developer and I do not really understand why or how everything works. I came across this method that worked for me and I thought I'd share it since I couldn't find a guide for my xperia phone when I needed it.
IN CASE SAFETY NET IS TRIGGERED, the only way to restore to everything in green is to reflash the stock rom (you don't have to format everything).
Did it work out for you? Just leave a reply saying that so I can figure out if everything works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
Thank you man
Great job
Hi there and great job. Many thanks for this.
I've a question, "(OPTIONAL BUT HIGHLY RECOMMENDED) Use flashtool to flash the modified version of the stock ROM from above (after you select the file there are 2 versions. pick the modified one)." - what if another .291 stock firmware is used (eg downloaded from Xperifirm)?
fribriz said:
Hi there and great job. Many thanks for this.
I've a question, "(OPTIONAL BUT HIGHLY RECOMMENDED) Use flashtool to flash the modified version of the stock ROM from above (after you select the file there are 2 versions. pick the modified one)." - what if another .291 stock firmware is used (eg downloaded from Xperifirm)?
Click to expand...
Click to collapse
Well, this worked on this exact version. If you don't use it, i can't guarantee it will work.
Well, can't either way
But it worked on that one. I believe you don't have to reinstall your stuff if you already have the stock rom. You can just flash it over without deleting anything
Works fine thank you
Adriano-A3 said:
Thank you man
Great job
Click to expand...
Click to collapse
Awesome
I'm actually surprised.
Doesn't work on elite kernel, just tested, no root and no safetynet
DahakePL said:
Doesn't work on elite kernel, just tested, no root and no safetynet
Click to expand...
Click to collapse
Have you tried with the advanced kernel I linked?
Also, you have to be running stock
Xperia z2
IceGordol said:
Have you tried with the advanced kernel I linked?
Also, you have to be running stock
Xperia z2
Click to expand...
Click to collapse
I'm using the advanced stock kernel method and it works 100%
But I tried elite kernel and it doesn't work at all, just in case someone else wanted to know or something :highfive:
DahakePL said:
I'm using the advanced stock kernel method and it works 100%
But I tried elite kernel and it doesn't work at all, just in case someone else wanted to know or something :highfive:
Click to expand...
Click to collapse
Modified the post in order to specify this. Also credited you. Thanks for this addition.
Where is modified FTF?
Sent from my D6503 using Tapatalk
Why do I need to flash TWRP? It is already included into advanced stock kernel.
After flash magisk, can't mount otg drive in twrp
Sent from my D6503 using Tapatalk
I am running a phone with KK 4.4.4 rooted and xposed installed. What should I do first to use it?
If I want to keep few apks data?
May I install Cyberian Camera MOd after it?
Thanks you! Working finally!
609125 said:
Thanks you! Working finally!
Click to expand...
Click to collapse
How u make it working? I got no clue about step 2... rootkernel old_boot.img new_boot.img? I really have no idea about the instructions...
---------- Post added at 04:10 PM ---------- Previous post was at 04:03 PM ----------
DahakePL said:
I'm using the advanced stock kernel method and it works 100%
But I tried elite kernel and it doesn't work at all, just in case someone else wanted to know or something :highfive:
Click to expand...
Click to collapse
Guys, I once rooted my Z2 with SuperSU in locked bootloader condition (already unroot it). Im interested with magisk and want to try it. Is it possible for me even my device is bootloader locked? Thank you
IceGordol said:
9) Open cmd and use cd to navigate to the folder in which you copied adb. Type in the console "fastboot flash boot New_boot.img". Turn off your phone and then hold Volume Up whil plugging it into your pc(booting it into fastboot).
Click to expand...
Click to collapse
Perfect for me. Thank you very much!
But your step 9 is wrong. should be "fastboot flash boot patched_boot.img"
My ROM is Marshmallow_Stock_575_ROM_Ultraslim
must remove SuperSU (root) before installing, use UPDATE-unSU-signed.zip
Can't get this to work at all. I'm on Customised UK stock ROM.
No matter what I do, I get bootloops once Magisk is installed. If I use the Magisk Uninstaller from TWRP the phone works fine again.
EDIT: I should have said, I've tried with Magisk 16.0 and 16.7 Beta. No luck with either. I've also tried patching the advanced stock kernel boot.img and I've tried installing via TWRP with Bootloader-SonyELF. No luck again, just the same bootloop!
UPDATE: I managed to fix this by using the latest version of the RootKernel patching tool (v5.23) instead of v4.31 and following the rest of the instructions using the boot.img from advanced stock kernel with Magisk 16.7 installed successfully.
Work fine with Magisk 18
okay after two soft brick, red blinking light and the device wont turn on, i finally succeed installing this. the first issue i'm getting is adb command not found when running the "fastboot flash boot patched_boot.img", so i tried to use TWRP to install the img, which refuse saying it need bootbridge, so i install through the recommend option in magisk manager (installing directly) which cause the first brick
the first brick is restored by using flash tool
the second brick can't be restored by flash tool due to the usb debugging is off causing flash tool to said "device connected but using old drivers", luckily xperia companion software (now called emma) restored it succesfully
and i finally figured what causing the soft brick, since emma said the bootloader is locked and magisk can't be used with locked bootloader and that bricked the device.
anyway finally unlocked the bootloader since emma needed it to unbrick the device. and after unlocking the bootloader and follow again the procedure here i finally succeed installing magisk on my z2
TLDR: YOU NEED UNLOCKED BOOTLOADER TO FOLLOW THIS PROCEDURE. to check easily if your bootloader is locked or not is just by running Emma (xperia updater replacement) or use "fastboot oem device-info".
finally can try magisk, since many apps detect supersu now and refuse to work with it. i didn't unlocked the bootloader the first time since supersu can work with locked bootloader >_>
Hi all!
For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch between custom and stock roms simply wasn't good enough for me. After lots of searching around, failed attempts, and some guidance by @Xennet, @osm0sis, and @nathanchance (thank you all for your help), I finally got a working solution. Ironically, it was under my nose the whole time.
@topjohnwu figured much of this out a while ago with his magiskboot binary - just modify the fstabs. Magiskboot only works for fstabs in the ramdisk though and dm-verity and forceencrypt are only disabled under certain conditions (when you create a .magisk file with the variables set to false and place it in the proper location). So I made an installker with AK3 by @osm0sis and used a combination of sed patches by @jcadduono in addition to others I found for fstabs not in the ramdisk, modified magiskboot with some extra entries I found need to be removed on some devices, and added some stuff of my own like the creation of .magisk and .supersu files in the right location with the proper contents.
The end result: a zip that will remove dm-verity and/or forceencrypt from all fstabs on your device
It can also remove disk quota if you choose. This may be needed if you have an older twrp and/or want to downgrade to Nougat. More info here: https://source.android.com/devices/storage/faster-stats
Instructions:
The zipname tells the installer what to do. Here are the current options:
Add 'enfec' or en'forceencrypt' to zipname to keep forceencrypt enabled if present
Add 'fec' or 'forceencrypt' to zipname to disable forceencrypt (zipname already has this so remove these if you want to keep it enabled)
Add 'quota' to zipname to disable disc quota
Note that verity is always disabled - it has to be for any modifications with this mod
If you're currently encrypted:
BACKUP YOUR INTERNAL STORAGE TO YOUR PC
Format data (this is NOT the same as Wipe data) (In TWRP: Wipe -> Format Data)
Reboot back into recovery
Follow the directions below for when you're not encrypted
If you're not encrypted: flash all of your stuff, then FLASH THIS ZIP LAST
Some extra details for Slot devices:
Flash ROM
Flash TWRP Installer Zip
Reboot into TWRP
Flash everything else
Flash this zip
Only difference here is the twrp zip and the recovery reboot, main principle is the same - FLASH THIS ZIP LAST
Troubleshooting:
Take a recovery log after flashing this zip (thanks to @aIecxs for the imgs):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If the zip isn't patching any fstabs that it should be, then it's possible that the previous zip(s) didn't unmount system and/or vendor properly. Either unmount them in twrp, or just reboot back into recovery and flash this zip again
Compatibility: Any android device
Source: https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt
Download
Zackptg5 said:
Hi all!
For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch between custom and stock roms simply wasn't good enough for me. After lots of searching around, failed attempts, and some guidance by @Xennet, @osm0sis, and @nathanchance (thank you all for your help), I finally got a working solution. Ironically, it was under my nose the whole time.
@topjohnwu figured much of this out a while ago with his magisk installer. However, dm-verity and forceencrypt (fec) are only disabled under certain conditions (when you create a .magisk file with the variables set to false and place it in the proper location). This would be fine for magisk users, but not for everyone else. So I took Magisk 16.6 beta zip, modified it to add fstab patches by @jcadduono, added some stuff of my own, and then gutted all of the magisk stuff unrelated to this.
The end result: a zip that will remove dm-verity and fec from your boot img and fstab files (without installing magisk, I took all of that out).
Instructions:
If you're currently encrypted: BACKUP YOUR INTERNAL STORAGE TO YOUR PC. Then format data. Reboot back into recovery
After doing that or if you're not encrypted: Flash your rom, custom kernel and/or root (like magisk or supersu), then this zip.
This zip should probably be flashed after anything that modifies your boot img (magisk, supersu, other root solutions, custom kernel, etc.).
Compatibility: Any device magisk is compatible with
Source:https://github.com/Zackptg5/Disable_Dm-Verity_FEC
Click to expand...
Click to collapse
Hi!
Just to be sure, does this remove the need to flash patched boot.img files when updating stock ROMs with root?
Thanks!
Sent from my OnePlus 3T using XDA Labs
@Zackptg5 Thanks for the zip! I trust this will work for both -- Treble and non-Treble ROMs, yes?
rippledrums said:
Hi!
Just to be sure, does this remove the need to flash patched boot.img files when updating stock ROMs with root?
Thanks!
Click to expand...
Click to collapse
Not sure what you mean. This does patch the boot img to remove verity/fec though if that's what you're getting at
shadowstep said:
@Zackptg5 Thanks for the zip! I trust this will work for both -- Treble and non-Treble ROMs, yes?
Click to expand...
Click to collapse
Yup
Zackptg5 said:
Not sure what you mean. This does patch the boot img to remove verity/fec though if that's what you're getting at
Click to expand...
Click to collapse
I found this because I saw your post in @Xennet's thread for OP3/3T Oxygen OS patched boot.img files.
Currently every time I update OOS I flash a boot.img patched by him and also a zip by him as well. What I'm asking is if your zip would be enough?
Sent from my OnePlus 3T using XDA Labs
rippledrums said:
I found this because I saw your post in @Xennet's thread for OP3/3T Oxygen OS patched boot.img files.
Currently every time I update OOS I flash a boot.img patched by him and also a zip by him as well. What I'm asking is if your zip would be enough?
Click to expand...
Click to collapse
Oh, gotcha. Ya, this zip handles that so you don't need to flash the boot img anymore
Zackptg5 said:
Oh, gotcha. Ya, this zip handles that so you don't need to flash the boot img anymore
Click to expand...
Click to collapse
Awesome, thanks! :laugh:
Sent from my OnePlus 3T using XDA Labs
@Zackptg5 First of all, great job. This looks very impressive and I appreciate the work you've done. I know this will be very useful for people trying things like the P GSI image then going back to no treble ROMs back on Oreo. I was just wondering though, as I have no intention on trying any treble ROMs, is there any benefit to using this over the old no verity V2 zip for someone that will only use non-treble Oreo ROMs. Thank you
DEVILOPS 007 said:
@Zackptg5 First of all, great job. This looks very impressive and I appreciate the work you've done. I know this will be very useful for people trying things like the P GSI image then going back to no treble ROMs back on Oreo. I was just wondering though, as I have no intention on trying any treble ROMs, is there any benefit to using this over the old no verity V2 zip for someone that will only use non-treble Oreo ROMs. Thank you
Click to expand...
Click to collapse
It really depends on the rom. If you're on a custom rom the old zip is probably fine (but not always, lots of variation there). If you're on a stock or stock based rom however, this is needed (unless you flash a patched boot.img - but why flash 2 things when you can flash 1?). This zip works with treble and nontreble roms by the way and the old zip can be easily modified the same way (I have one floating around xda somewhere).
Assuming you're on a custom rom which already has dm-verity disabled, the benefit to this zip is that not only does it disable force encryption in the vendor fstabs (like the old zip), but it also disables it in the boot img which some roms have
Zackptg5 said:
It really depends on the rom. If you're on a custom rom the old zip is probably fine (but not always, lots of variation there). If you're on a stock or stock based rom however, this is needed (unless you flash a patched boot.img - but why flash 2 things when you can flash 1?). This zip works with treble and nontreble roms by the way and the old zip can be easily modified the same way (I have one floating around xda somewhere).
Assuming you're on a custom rom which already has dm-verity disabled, the benefit to this zip is that not only does it disable force encryption in the vendor fstabs (like the old zip), but it also disables it in the boot img which some roms have
Click to expand...
Click to collapse
So basically it is a more well-done version if you want to put it that way. Works on stock and custom ROMs including treble no matter what it is or if there is dm-verity enabled or not is what I'm understanding from this. I'm using treskmod currently which is basically OmniRom. I'll give it a go when I get back off holiday so I can clean flash. Thanks again?
DEVILOPS 007 said:
So basically it is a more well-done version if you want to put it that way. Works on stock and custom ROMs including treble no matter what it is or if there is dm-verity enabled or not is what I'm understanding from this. I'm using treskmod currently which is basically OmniRom. I'll give it a go when I get back off holiday so I can clean flash. Thanks again?
Click to expand...
Click to collapse
I wouldn't call it more well done but rather more complete
And yup, should work on any rom/device magiskboot is able to work with (which is most of them). Dm-verity will be removed too by this mod by the way
@Zackptg5 hi. Tell me please how need me right do. I am on LOS 15.1 on my Samsung Tab A SM-T585.now. And with dm-verity and fec are all right. But when i go on custom rom based on stock 8.0(port) i got dm-verity and fec issue. After installation this rom and start i can see all files of internal memory in file explorer. But only i reboot to recovery internal memory have size 0mb. So my question: i need do fomat data before installtion rom and your zip or only install zip?
Zackptg5 said:
I wouldn't call it more well done but rather more complete
And yup, should work on any rom/device magiskboot is able to work with (which is most of them). Dm-verity will be removed too by this mod by the way
Click to expand...
Click to collapse
@DEVILOPS 007 I just flashed latest 20180719 tresk and tried this zip and got sent back to TWRP. Immedietly flashed v2 and it booted. It worked on AOSiP earlier though so not sure what could cause it to fail here.
Sent from my OnePlus5T using XDA Labs
repey6 said:
@Zackptg5 hi. Tell me please how need me right do. I am on LOS 15.1 on my Samsung Tab A SM-T585.now. And with dm-verity and fec are all right. But when i go on custom rom based on stock 8.0(port) i got dm-verity and fec issue. After installation this rom and start i can see all files of internal memory in file explorer. But only i reboot to recovery internal memory have size 0mb. So my question: i need do fomat data before installtion rom and your zip or only install zip?
Click to expand...
Click to collapse
You'll need to format data. Then flash rom and kernel, then this after
bdwilk said:
@DEVILOPS 007 I just flashed latest 20180719 tresk and tried this zip and got sent back to TWRP. Immedietly flashed v2 and it booted. It worked on AOSiP earlier though so not sure what could cause it to fail here.
Click to expand...
Click to collapse
Can you send a recovery log? What all did you flash when that happened and in what order? Thanks
Zackptg5 said:
You'll need to format data. Then flash rom and kernel, then this after
Can you send a recovery log? What all did you flash when that happened and in what order? Thanks
Click to expand...
Click to collapse
Format data everytime or just once for this to work or format because of treble or what? I'm curious as to when formatting is required and why exactly.
Zackptg5 said:
You'll need to format data. Then flash rom and kernel, then this after
Can you send a recovery log? What all did you flash when that happened and in what order? Thanks
Click to expand...
Click to collapse
I'll do it again and get a log for you another time.
ROM, magisk 16.6, vanced installer (YouTube), universal dm-verity (ROM has built-in gapps)
Got sent back to TWRP and hit reboot to system one more time for science, and got sent back to TWRP again.
Flashed dm-verity v2 and it booted fine.
OnePlus 5t
DEVILOPS 007 said:
Format data everytime or just once for this to work or format because of treble or what? I'm curious as to when formatting is required and why exactly.
Click to expand...
Click to collapse
I believe he's just telling dude how to decrypt for the first time.
Sent from my OnePlus5T using XDA Labs
bdwilk said:
I'll do it again and get a log for you another time.
ROM, magisk 16.6, vanced installer (YouTube), universal dm-verity (ROM has built-in gapps)
Got sent back to TWRP and hit reboot to system one more time for science, and got sent back to TWRP again.
Flashed dm-verity v2 and it booted fine.
OnePlus 5t
I believe he's just telling dude how to decrypt for the first time.
Click to expand...
Click to collapse
Oh I thought he was responding to you. My bad lol
DEVILOPS 007 said:
Oh I thought he was responding to you. My bad lol
Click to expand...
Click to collapse
Ya, you just need to format data to decrypt
Zackptg5 said:
You'll need to format data. Then flash rom and kernel, then this after
Click to expand...
Click to collapse
This is a copypaste from Samsuyng Tab A thread:
repey6 said:
Hi. You can to try Universal DM-Verity and ForceEncrypt Disabler by Zackptg5 from this thred https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
blaz3gamingHD said:
Does this work?
---------- Post added at 09:52 PM ---------- Previous post was at 09:20 PM ----------
I've tested it and it doesn't work, still encrypted.
Click to expand...
Click to collapse
repey6 said:
This is a copypaste from Samsuyng Tab A thread:
Click to expand...
Click to collapse
Of course he's still encrypted this zip isn't going to decrypt your phone. It's for once your decrypted and flashing a rom it will not allow the rom zip to encrypt your device and will allow it to boot decrypted and without the insecure verity check blocking boot.
Sent from my ONEPLUS A5010 using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to Team OpenKirin AOSP Project. Our goal is to provide
a overall stable AOSP experience across all Huawei/Honor phones
utilizing a Kirin SoC and EMUI 8.0 - either updated or shipped.
So far most of the bugs have been fixed and the ROMs are fully usable
as daily driver - and fully Kirin optimized.
This is the device support section for: Huawei P10.
Any bugs found on this device(s) can be reported here, please include proper logs if you encounter any issues.
We support 3 ROMs in total as of now - LineageOS (Unofficial), ResurrectionRemix OS (Official from Beta 2+), OmniRom
You can find all needed guides/roms on our official website: https://openkirin.net
Requirements: basically full stock EMUI 8.0, with stock recovery/ramdisk
Support: Telegram - https://t.me/joinchat/EeDpi02ekfeJSBeaV4eqOw
XDA:DevDB Information
OpenKirin Treble ROMs, ROM for the Huawei P10
Contributors
OldDroid, XePeleato, surdu_petru
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: EMUI 8.0
Based On: LineageOS, ResurrectionRemix OS, OmniRom
Version Information
Status: Beta
Created 2018-08-13
Last Updated 2018-08-27
do you know anyway in which i could unlock my bootloader?
JohnnyMwanza said:
do you know anyway in which i could unlock my bootloader?
Click to expand...
Click to collapse
DC Unlocker is the only way to go as Huawei stopped releasing bootloader unlock codes since July 22, 2018.
I installed the Resurrection Remix and Lineage rom on my P10+ (VKY L29) device and both got me the same problem:
When i boot (the boot is successful), Google starts the first configuration. It asks me the language and the visual properties and then i press "next". The screen remains on "Just a second..." for about forever.
I tried format data before and after, tried to install several Treble roms... Everything took me to the same problem.
I tried also to re-install Gapps, but this took me to another problem: the Google First Configuration is totally black.
What should i do?
McEyes said:
I installed the Resurrection Remix and Lineage rom on my P10+ (VKY L29) device and both got me the same problem:
When i boot (the boot is successful), Google starts the first configuration. It asks me the language and the visual properties and then i press "next". The screen remains on "Just a second..." for about forever.
I tried format data before and after, tried to install several Treble roms... Everything took me to the same problem.
I tried also to re-install Gapps, but this took me to another problem: the Google First Configuration is totally black.
What should i do?
Click to expand...
Click to collapse
Its a know glitch, just reboot and try again.
netmaniack said:
Its a know glitch, just reboot and try again.
Click to expand...
Click to collapse
I tried rebooting about 10 times and he always did the same.
Fortunately I figured out how to resolve this hell:
The Google first configuration setup checks the integrity of the ramdisk Partition. I had a custom recovery so obviously the check was not satisfied.
The solution is to flash the stock recovery ramdisk partition (in my case i download The Official update of Huawei p10 Plus and extracted only the ramdisk image).
When i finished the configuration I completed every setup and then I reinstalled the custom recovery again.
McEyes said:
Fortunately I figured out how to resolve this hell:
The Google first configuration setup checks the integrity of the ramdisk Partition. I had a custom recovery so obviously the check was not satisfied.
The solution is to flash the stock recovery ramdisk partition (in my case i download The Official update of Huawei p10 Plus and extracted only the ramdisk image).
When i finished the configuration I completed every setup and then I reinstalled the custom recovery again.
Click to expand...
Click to collapse
If you have properly read the instructions in OpenKirin website, it was clearly stated there that all these ROMs must be installed wirh stock recovery to avoid other issues.
ej8989 said:
If you have properly read the instructions in OpenKirin website, it was clearly stated there that all these ROMs must be installed wirh stock recovery to avoid other issues.
Click to expand...
Click to collapse
True, I've read the disclaimer, but if someone, like me, used to install ROMs with the same warning without any problem (like an AOSP rom on my previous phone, which I installed having the TWRP), maybe he/she would think that there is not so much to worry about.
However, I noticed that there isn't a real "guide" on internet about a workaround of the "Just a sec" problem, so I wrote that message also for who needs a help and does not know about the partition check.
I found a bug on the "display" menu.
When i select a theme (light, dark, or the black switch), the system theme doesn't change at all. Tried to reboot, clear cache and data of SystemUI, nothing changed.
I bypassed this theme issue with Substratum. Didn't get any bug/problem with Substratum.
Device: P10 plus VKY-L29
Rom: Resurrection Remix 6.1.0 - Oreo - 2018.08.18
McEyes said:
I found a bug on the "display" menu.
When i select a theme (light, dark, or the black switch), the system theme doesn't change at all. Tried to reboot, clear cache and data of SystemUI, nothing changed.
I bypassed this theme issue with Substratum. Didn't get any bug/problem with Substratum.
Device: P10 plus VKY-L29
Rom: Resurrection Remix 6.1.0 - Oreo - 2018.08.18
Click to expand...
Click to collapse
for me working normal
how to root ? can i flash normal magisk or need special for huawei device?
doktor29 said:
for me working normal
how to root ? can i flash normal magisk or need special for huawei device?
Click to expand...
Click to collapse
If you use a normal Huawei EMUI system, there is a special treatment which use a special SuperSu zip file.
Also, you can use a Magisk version, always optimized for Huawei. I found the zip variant in a thread in the P10+ section.
If you have the Treble ROM, which is the main topic of the thread, I did this:
Ensured that there were no setups to do;
Re-flashed TWRP;
Installed the normal Magisk zip from TWRP.
Because is not a EMUI system anymore, you can easily install every mod or patch you wish.
Personal note: I tried install SuperSu with the zip, but the app said "binary occupied". Since it did like that before, with the EMUI system, I gave up and I installed Magisk.
Now it works like a charm.
McEyes said:
If you use a normal Huawei EMUI system, there is a special treatment which use a special SuperSu zip file.
Also, you can use a Magisk version, always optimized for Huawei. I found the zip variant in a thread in the P10+ section.
If you have the Treble ROM, which is the main topic of the thread, I did this:
Ensured that there were no setups to do;
Re-flashed TWRP;
Installed the normal Magisk zip from TWRP.
Because is not a EMUI system anymore, you can easily install every mod or patch you wish.
Personal note: I tried install SuperSu with the zip, but the app said "binary occupied". Since it did like that before, with the EMUI system, I gave up and I installed Magisk.
Now it works like a charm.
Click to expand...
Click to collapse
can you link magisk version?
i try many official but i get info "unable to detect boot image"
doktor29 said:
can you link magisk version?
i try many official but i get info "unable to detect boot image"
Click to expand...
Click to collapse
This is the thread:
https://forum.xda-developers.com/p10-plus/development/magisk-p10-p10plus-t3752482
It says is good even for P10.
you must flash it with TWRP
McEyes said:
This is the thread:
https://forum.xda-developers.com/p10-plus/development/magisk-p10-p10plus-t3752482
It says is good even for P10.
you must flash it with TWRP
Click to expand...
Click to collapse
what version of recovery You use ? because still wont work, i have 3.1.1 for oreo
you have dencrypted or encrypted data ? i try to decrypt but still in recovery i dont see anything in data partition
Don't use twrp with openkirin rom's. Join the telegram openkirin group and u will get there all the help u need. U need magisk 16.7 or newer. I don't understand why people still use twrp when is stated so many times that using twrp with openkirin rom's usually leed's to bootlop.
any chance to get rid of this annoying notification of SDCARD after reboot ?
rom ressurection remix
---------- Post added at 09:52 PM ---------- Previous post was at 09:33 PM ----------
antiratar said:
Don't use twrp with openkirin rom's. Join the telegram openkirin group and u will get there all the help u need. U need magisk 16.7 or newer. I don't understand why people still use twrp when is stated so many times that using twrp with openkirin rom's usually leed's to bootlop.
Click to expand...
Click to collapse
so how i can flash magisk without twrp ?
for me it works only data partition is not vivible due to encryption
can someone test fingerprint after reboot ?
i have strange issue, after reboot my fingerprint is not recognized anymore :/
if i add new one is ok till next reboot, then again my FP is not recognizing.
and no i dont mean it wont work berofre i put PIN/Passoword after reboot it wont work at all after reboot till i add next one :/
it happen in RR and Carbon, other roms i dont test
doktor29 said:
can someone test fingerprint after reboot ?
i have strange issue, after reboot my fingerprint is not recognized anymore :/
if i add new one is ok till next reboot, then again my FP is not recognizing.
and no i dont mean it wont work berofre i put PIN/Passoword after reboot it wont work at all after reboot till i add next one :/
it happen in RR and Carbon, other roms i dont test
Click to expand...
Click to collapse
Are you on stock kernel? Does this happen ALL the time or just random?
doktor29 said:
so how i can flash magisk without twrp ?
Click to expand...
Click to collapse
Instructions here: https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
You only need to use fastboot.
ej8989 said:
Are you on stock kernel? Does this happen ALL the time or just random?
Instructions here: https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
You only need to use fastboot.
Click to expand...
Click to collapse
it happen to me every reboot :/
i have only magisk with stock recovery, from instruction above
doktor29 said:
what version of recovery You use ? because still wont work, i have 3.1.1 for oreo
you have dencrypted or encrypted data ? i try to decrypt but still in recovery i dont see anything in data partition
Click to expand...
Click to collapse
I use the FromFutureRom version that is in the thread I linked before. I think is made especially for Huawei P10/P10+
My data partition is still encrypted.
In order to decrypt data you should format the so called "user data", which is the combination of /data and /sdcard. Don't have to say that you will lose everything on your internal archive, so be sure to backup everything. The external SD card will NOT be affected.
In the TWRP you can to this on the menu "format" -> "format data" -> write "yes" and format everything.
---------- Post added at 02:15 PM ---------- Previous post was at 02:14 PM ----------
antiratar said:
Don't use twrp with openkirin rom's. Join the telegram openkirin group and u will get there all the help u need. U need magisk 16.7 or newer. I don't understand why people still use twrp when is stated so many times that using twrp with openkirin rom's usually leed's to bootlop.
Click to expand...
Click to collapse
You are absolutely right, but I said that you can install TWRP or any custom rom AFTER the Treble Rom installation. I am now on Resurrection Remix Treble rom, with a TWRP recovery installed after the rom flash and everything is fine since the first boot.
Hello,
My goal is to get an Android 11 Stable version with TWRP recovery and magisk root.
I cannot achieve this goal cause of an error - "Qualcomm crashdump" - i get when trying to boot into TWRP.IMG
Does anyone managed to install twrp recovery and root with Android 11 stable?
Thanks
BenoMosko said:
Hi!
First Thanks for the reply.
Second, I opened a thread just for that, maybe you can share your wisdom with us over there
Stable Oxygen OS/Android 11 fastboot boot twrp.img lead to Qualcomm Crashdump
Hello, My goal is to get an Android 11 Stable version with TWRP recovery and magisk root. I cannot achieve this goal cause of an error - "Qualcomm crashdump" - i get when trying to boot into TWRP.IMG Does anyone managed to install twrp...
forum.xda-developers.com
I dont have a T-Mobile OP6T i have a global device.
"it could work to set up a rooted OOS 10 (which should give you less trouble) and then use the method I described above to upgrade."
Can you share and give us step by step instruction please?
Which version should i be on with installing twrp recovery and root using magisk?
10.3.8?
10.3.12?
cant i do it straight from 11?
thanks.
Click to expand...
Click to collapse
I believe there's a rollback zip which could help you out. It's at the bottom of this article. Not sure if it works on stable. Note that it wipes everything!
scorpio76r said:
Yes, I have the T-Mobile which is internationally converted
Click to expand...
Click to collapse
TMO has not been very kind to development in any way. It may just take some time for modding to catch up or you may find a way. Much luck finding the answer I personally stay as far away from provider branded devices as I can
Timmmmaaahh! said:
I believe there's a rollback zip which could help you out. It's at the bottom of this article. Not sure if it works on stable. Note that it wipes everything!
TMO has not been very kind to development in any way. It may just take some time for modding to catch up or you may find a way. Much luck finding the answer I personally stay as far away from provider branded devices as I can
Click to expand...
Click to collapse
You are so correct. I will never purchase a carrier branded device again.
Timmmmaaahh! said:
I believe there's a rollback zip which could help you out. It's at the bottom of this article. Not sure if it works on stable. Note that it wipes everything!
TMO has not been very kind to development in any way. It may just take some time for modding to catch up or you may find a way. Much luck finding the answer I personally stay as far away from provider branded devices as I can
Click to expand...
Click to collapse
Hi,
I have the rollbacks and i can use mstool to do rollbacks to 10.3.8
that's not my issue.
Lets organize it.
I have a goal - OnePlus 6T with OOS11+TWRP+ROOT
can i achieve this goal?
if yes,
can u please give me details on how to achieve?
thanks.
BenoMosko said:
Hi,
I have the rollbacks and i can use mstool to do rollbacks to 10.3.8
that's not my issue.
Lets organize it.
I have a goal - OnePlus 6T with OOS11+TWRP+ROOT
can i achieve this goal?
if yes,
can u please give me details on how to achieve?
thanks.
Click to expand...
Click to collapse
This would also be helpful to people who are just purchasing this device which most likely will have the 11 update already
BenoMosko said:
Hi,
I have the rollbacks and i can use mstool to do rollbacks to 10.3.8
that's not my issue.
Lets organize it.
I have a goal - OnePlus 6T with OOS11+TWRP+ROOT
can i achieve this goal?
if yes,
can u please give me details on how to achieve?
thanks.
Click to expand...
Click to collapse
With an international version, I don't see any reason why it wouldn't work. After MSM'ing (whichever version) I'd first make sure it gets a working TWRP and Magisk root, then upgrade to latest 10 keeping the method I described in mind (to keep TWRP and root alive), then take the same step towards 11. I don't think it even matters which 10 is present, the full stable 11 zip will upgrade it either way. I was one (security) update behind.
Timmmmaaahh! said:
With an international version, I don't see any reason why it wouldn't work. After MSM'ing (whichever version) I'd first make sure it gets a working TWRP and Magisk root, then upgrade to latest 10 keeping the method I described in mind (to keep TWRP and root alive), then take the same step towards 11. I don't think it even matters which 10 is present, the full stable 11 zip will upgrade it either way. I was one (security) update behind.
Click to expand...
Click to collapse
Thank you so much for the support
"keeping the method I described in mind"
can you please copy paste it here?
and maybe do a little
1.
2.
3.
steps instructions please????????
thanks.
BenoMosko said:
Thank you so much for the support
"keeping the method I described in mind"
can you please copy paste it here?
and maybe do a little
1.
2.
3.
steps instructions please????????
thanks.
Click to expand...
Click to collapse
I already did
Timmmmaaahh! said:
That makes SafetyNet pass? I did the classic routine:
Install full zip (OnePlus6TOxygen_34.J.60) via 'Local upgrade' - no rebooting
Flash TWRP installer (I had 3.4.0-11) via Magisk - no rebooting
Flash Magisk via Magisk to other slot
Reboot! All done.
Click to expand...
Click to collapse
Timmmmaaahh! said:
I already did
Click to expand...
Click to collapse
Great, Thanks.
One more question...
when going back to 10.3.8 to install twrp, can i use the latest twrp version and not "3.4.0-11"?
thanks.
Timmmmaaahh! said:
I already did
Click to expand...
Click to collapse
Hi ..Will the twrp version 3.5.2-9 work too? Or do we have to use this version in your post?
Would flashing OOS 10 back clear all my data? Is there way to just install the TWRP and root it with magisk zip like we did earlier?
shreyas.kukde said:
Would flashing OOS 10 back clear all my data? Is there way to just install the TWRP and root it with magisk zip like we did earlier?
Click to expand...
Click to collapse
It has been a no go so far trying to get magisk and twrp on 11. I guess we will need to use the msm tool and,start from scratch
BenoMosko said:
Great, Thanks.
One more question...
when going back to 10.3.8 to install twrp, can i use the latest twrp version and not "3.4.0-11"?
thanks.
Click to expand...
Click to collapse
Libraplum76 said:
Hi ..Will the twrp version 3.5.2-9 work too? Or do we have to use this version in your post?
Click to expand...
Click to collapse
I really don't think versions are all that important. Try the latest one and work your way down from there? Best practice IMHO is just revisiting the TWRP thread when preparing to flash and check for any anomalies in OP and last 2 or 3 pages of the thread. Do the same for anything you need to flash (Magisk, OOS or custom ROM thread, etc.). More reading lowers the chances of failure.
Just use fastboot flash boot_a boot.img and preferably fastboot flash boot_b boot.img, instead of boot.img use beta3 prerooted and preinstalled with twrp boot image - you can find it somewhere on this forum in another section. Then just from fasboot boot to recovery and install oos11 again.
ppajdek said:
Just use fastboot flash boot_a boot.img and preferably fastboot flash boot_b boot.img, instead of boot.img use beta3 prerooted and preinstalled with twrp boot image - you can find it somewhere on this forum in another section. Then just from fasboot boot to recovery and install oos11 again.
Click to expand...
Click to collapse
You just brung hope, thank you. I will definitely go on the hunt for that recovery image*Edit, just found the link https://forum.xda-developers.com/t/...1-open-beta-2-and-open-beta-3-latest.4316563/
This has been solved for the oneplus 6t international converted on Oxygen 11 stable. Using the PRO3 file from the link I posted earlier (shout out to member KizuYuna who made and, provided the PRO3 file, also shout out to ppajdek for pointing me in the right direction ) I fastboot flash boot the file (simple drag and drop) it brought me to a twrp called pitch black( yaay! I had some form of twrp) while in there I flashed the 3.5.1_9-0 fajita installer zip. Next, I hit the power button in the pitch black twrp that gave me a option to reboot to recovery. Yaay, I rebooted to twrp 3,5.1_9-0. Next I flashed the latest 11 oxygen stable. After that I flashed the twrp installer again. After that, I rebooted to recovery (was glad I hadn't bricked by now) Next, I flashed magisk 23.0 and, lastly rebooted to system. (shocked that I didn't get a crash dump screen, lol) went into magisk and, enabled magisk hide. Here are pictures of the result, yaay. I did not post a picture of twrp, but yes it works and is present.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
scorpio76r said:
This has been solved for the oneplus 6t international converted on Oxygen 11 stable. Using the PRO3 file from the link I posted earlier (shout out to member KizuYuna who made and, provided the PRO3 file, also shout out to ppajdek for pointing me in the right direction ) I fastboot flash boot the file (simple drag and drop) it brought me to a twrp called pitch black( yaay! I had some form of twrp) while in there I flashed the 3.5.1_9-0 fajita installer zip. Next, I hit the power button in the pitch black twrp that gave me a option to reboot to recovery. Yaay, I rebooted to twrp 3,5.1_9-0. Next I flashed the latest 11 oxygen stable. After that I flashed the twrp installer again. After that, I rebooted to recovery (was glad I hadn't bricked by now) Next, I flashed magisk 23.0 and, lastly rebooted to system. (shocked that I didn't get a crash dump screen, lol) went into magisk and, enabled magisk hide. Here are pictures of the result, yaay. I did not post a picture of twrp, but yes it works and is present. View attachment 5384313View attachment 5384315
Click to expand...
Click to collapse
Great! Worked for me too. Thought I could never get Root or Twrp again.
scorpio76r said:
It has been a no go so far trying to get magisk and twrp on 11. I guess we will need to use the msm tool and,start from scratch
Click to expand...
Click to collapse
A telegram group titled OnePlus 6T Chat has a user who said he flashed latest TWRP and Latest Magisk and it worked for him. Strange..
shreyas.kukde said:
A telegram group titled OnePlus 6T Chat has a user who said he flashed latest TWRP and Latest Magisk and it worked for him. Strange..
Click to expand...
Click to collapse
Shocking, lol
scorpio76r said:
Shocking, lol
Click to expand...
Click to collapse
Can you provide the TWRP zip that you flashed?