Related
Hello folks,
I have a Pixel sailfish and I am on Nougat 7.1.2. I would like to just root it via Magisk. Bootloader is unlocked and i tried the latest version of TWRP 3.2.1.2 and latest Magisk 16.0, Magisk Manager is 5.7. Heres the problem, if I tried to flash TWRP and then reboot into recovery (to check if TWRP sticks) I could not access my files because they are all encrypted. I did removed all pass codes, fingerprint etc. Is there a specific version of TWRP, Magisk that I need to install on Nougat 7.1.2? My process is as follow (assume fresh Nougat is onboard):
1. Boot into bootloader
2. Fastboot twrp zip
3. In twrp, flash twrp .zip
4. Reboot into recovery to see if twrp sticks
5. If 4 passes, then flash Magisk zip (version 16)
6. Reboot into system
7. Install Magisk manager apk file
8. Open Magisk manager.
Please let me know,
Thank you very much
I would like to point out that my main goals are: run stock 7.1.2 and root. That's it, no fancy kernels or anything. 8.1 and 8.0 stock are killing my battery so i would like to do some tests on 7.1.2.
You can try set a pin, twrp in nougat worked perfectly.
So when you go in twrp with a pin set, it will 100% ask you the pin for decrypt.
Also, not sure if you made a writing mistake, but you have to fastboot the img, not the zip of twrp
Thanks for this but i still have the same problem. Setting pin in Nougat, then reboot into bootloader, fastboot the .img file works. When in TWRP, it asks for my pin, i enter and manage to decrypt my data. Then I proceed to flash install tpwrp.zip. Process ends well but then when I reboot the phone, then reboot into TWRP (already installed). TWRP is there which means that the installation process is ok. However, this time, it does not ask for my PIN, there is only a slide bar to "Swipe to allow modifications". I did so and my file manager only has a bunch of files with weird letters. I assume these are encrypted. Obviously, I cannot flash install Magisk.zip here. So I tried the following:
1. Fastboot the twrp.img to get into TWRP
2. Do not install TWRP but go to file manager and flash the Magisk.zip
3. The process ended well. I rebooted
4. Phone booted fine. I then installed Magisk Manager v5.7 (latest from XDA) via apk.
5. Installation ended ok.
6. I opened up Magisk Manager and got stuck at the Boot Logo.
I hope these are detailed, please let me know if you can help me.
Thank you very much
TENN3R said:
You can try set a pin, twrp in nougat worked perfectly.
So when you go in twrp with a pin set, it will 100% ask you the pin for decrypt.
Also, not sure if you made a writing mistake, but you have to fastboot the img, not the zip of twrp
Click to expand...
Click to collapse
maxwell0312 said:
... there is only a slide bar to "Swipe to allow modifications". I did so and my file manager only has a bunch of files with weird letters. I assume these are encrypted...
Click to expand...
Click to collapse
Looks like some kinda problem with this twrp version.
Have you tried an older one, just to be sure? From what I remember, latest version made for nougat was 3.1.1 (?) but I'm not sure.
Maybe just try a 3.2.0, for example. Just boot it to avoid problems, don't flash the zip since you are not sure.
Otherwise, you can always try the manual boot.img patch method for magisk, so you don't have to use a recovery (official magisk thread -> installation instructions -> Via magisk manager)
These are only my ideas, not sure if they're gonna work or not.
TENN3R said:
Looks like some kinda problem with this twrp version.
Have you tried an older one, just to be sure? From what I remember, latest version made for nougat was 3.1.1 (?) but I'm not sure.
Maybe just try a 3.2.0, for example. Just boot it to avoid problems, don't flash the zip since you are not sure.
Otherwise, you can always try the manual boot.img patch method for magisk, so you don't have to use a recovery (official magisk thread -> installation instructions -> Via magisk manager)
These are only my ideas, not sure if they're gonna work or not.
Click to expand...
Click to collapse
Thank you very much for your help, I managed to fix and make TWRP stick, so no problem there. Problem now is Magisk doesnt work. Is there a problem with my order:
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
If anyone has any ideas, please let me know.
Thank you
maxwell0312 said:
...
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
...
Click to expand...
Click to collapse
I think for this you better ask in magisk forums. Stable version of magisk also installs the manager apk, I noticed that beta versions don't.
You can find better support in official magisk thread :good:
Hey
maxwell0312 said:
Thank you very much for your help, I managed to fix and make TWRP stick, so no problem there. Problem now is Magisk doesnt work. Is there a problem with my order:
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
If anyone has any ideas, please let me know.
Thank you
Click to expand...
Click to collapse
What version of TWRP did you use..More like what did you do..I am having the same problem.
I used TWRP 3.1.2.0 and 3.2.1.0. All failed. I figured that after flashing TWRP.zip via TWRP Recovery (which you get to after you do fastboot boot twrp.img from PC) , you would need to pick the correct Slot to reboot. Once you boot into the correct slot, then flashing Magisk.zip would work, I think. I kept messing around with reboot into A and B and got tired of it. Now I switched to Resurrection OS for sailfish, got all I want: theming and rootless support. I actually tried to go back to stock 7.1.2 myself to test if batteries improved. It turned out that it didnt really matter much. Also, if you are into Substratum theming like I do, its better to use an OMS rom
Fixed (update)
hardhead808 said:
What version of TWRP did you use..More like what did you do..I am having the same problem.
Click to expand...
Click to collapse
I flashed TWRP 3.1.1-1 then of course went in a recovery bootloop...Just flash SU..... PROFIT
maxwell0312 said:
I used TWRP 3.1.2.0 and 3.2.1.0. All failed. I figured that after flashing TWRP.zip via TWRP Recovery (which you get to after you do fastboot boot twrp.img from PC) , you would need to pick the correct Slot to reboot. Once you boot into the correct slot, then flashing Magisk.zip would work, I think. I kept messing around with reboot into A and B and got tired of it. Now I switched to Resurrection OS for sailfish, got all I want: theming and rootless support. I actually tried to go back to stock 7.1.2 myself to test if batteries improved. It turned out that it didnt really matter much. Also, if you are into Substratum theming like I do, its better to use an OMS rom
Click to expand...
Click to collapse
I found that when I use the uninstall magisk then flash magisk zip, if you watch closely, magisk will install some files to slot b also. Most of the time it will automatically download magisk manager. As far as battery life, my pixel XL was never better on 8.1. I installed the app is 9 preview 2 and my battery life is even better. You should move forward not back.
Good luck
fiverings said:
I found that when I use the uninstall magisk then flash magisk zip, if you watch closely, magisk will install some files to slot b also. Most of the time it will automatically download magisk manager. As far as battery life, my pixel XL was never better on 8.1. I installed the app is 9 preview 2 and my battery life is even better. You should move forward not back.
Good luck
Click to expand...
Click to collapse
What is your SOT when go back with root? Also, what are the versions of TWRP and magisk that you use?
maxwell0312 said:
What is your SOT when go back with root? Also, what are the versions of TWRP and magisk that you use?
Click to expand...
Click to collapse
TWRP version is 3.2.1-2
Magisk is 16.0 version
Magisk is 16.4 installed version
Magisk Manager is 5.7.0
I read somewhere that I should be on 16.2 or 16.3 I read that after I installed 16.4 it didn't work at first, but about 4 or more hours later it started working. I'm certified and pass all tests. After installing Magisk, I always clear cache & data from play store app, then clear just cache from play store services.
Sot, I usually can get around 8 with 15-20% left
Good Luck
fiverings said:
TWRP version is 3.2.1-2
Magisk is 16.0 version
Magisk is 16.4 installed version
Magisk Manager is 5.7.0
I read somewhere that I should be on 16.2 or 16.3 I read that after I installed 16.4 it didn't work at first, but about 4 or more hours later it started working. I'm certified and pass all tests. After installing Magisk, I always clear cache & data from play store app, then clear just cache from play store services.
Sot, I usually can get around 8 with 15-20% left
Good Luck
Click to expand...
Click to collapse
Thanks. I am on the smaller OG Pixel with 2770 mAh battery. I got 6h15 mins of SOT with 5% left. Not sure if this is normal
Was this problem ever resolved? I've been having problems that seem similar. I'm trying to use TWRP with Magisk and the stock google 9.0 for my Pixel, but I keep getting stuck. Wonder if someone has complete set of steps with specific versions of each of the necessary components.
bad post
DISCLAIMER:
I'm not the developer of any of those Roms, so don't cry on me if your device gets bricked!
INTRODUCTION:
So, as many of you guys know, the Homor 9 is Treble compatible which means you can get any Treble Rom on it although the support of our device on XDA is really poor on our forum.
IMPORTANT ISSUES:
Since we don't even have an official TWRP for the Honor 9 but only some kind of a buggy one with missing encryption on Android 8.1 (I mean I'm thankful for what we have, but it's still sad), I was NOT able to flash Gapps afterwards, which means, either you have to get a Rom with implemented Gapps or live without them.
If anyone finds out a way to install them, please let me know!
REQUIREMENTS:
- Unlocked bootloader
- Any Android Oreo firmware installed
- Stock Recovery (as our TWRP can't wipe stuff)
INSTALLATION:
1. Look for your favorite Rom on the following link and download it:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
2. Reboot your device to bootloader
3. "fastboot flash system [downloaded img file]"
4. Reboot to stock recovery
5. Wipe cache and factory reset
6. Reboot and enjoy!
I hope I was able to get some of your hopes up for Honor 9 and custom roms!
Thank u! But i have one question about this Treble Rom's... is all working? ( BT, WLAN, Sound ect.?)
nscounter said:
Thank u! But i have one question about this Treble Rom's... is all working? ( BT, WLAN, Sound ect.?)
Click to expand...
Click to collapse
Look at the bug list of each rom. As I said, I'm not the developer of any of those roms.
But I'm using the pure AOSP rom by phhusson and it's working perfectly fine without any issues as far as I can tell.
Is it compulsory to wipe data for a new ROM to work, say for example i'm going form AOSP 8 to AOSP 8.1, should the data partition be compatible and not require wiping?
Iv'e always wiped /data in the past, but i cant be bothered this time since i don't want to re-install everything.
ambitiousButRubbish said:
Is it compulsory to wipe data for a new ROM to work, say for example i'm going form AOSP 8 to AOSP 8.1, should the data partition be compatible and not require wiping?
Iv'e always wiped /data in the past, but i cant be bothered this time since i don't want to re-install everything.
Click to expand...
Click to collapse
I dirty flashed a few times - even going from AOSP to RROS for example and it went fine for me. So just try it out, reboot with only wiping cache and if you experience bugs you can still do a factory reset. But just keep in mind that many developers don't support dirty flashing because bugs can happen easily when doing that and it's also not recommended.
PS: Don't dirty flash a Rom without Gapps if you're using a launcher that requires Google Play Services!
_lucx_ said:
I dirty flashed a few times - even going from AOSP to RROS for example and it went fine for me. So just try it out, reboot with only wiping cache and if you experience bugs you can still do a factory reset. But just keep in mind that many developers don't support dirty flashing because bugs can happen easily when doing that and it's also not recommended.
PS: Don't dirty flash a Rom without Gapps if you're using a launcher that requires Google Play Services!
Click to expand...
Click to collapse
Excellent, thanks, I'll give it a try, I'll make sure I disable or uninstall xposed and disable substratum beforehand, I guess the worst that can happen is a bootloop, and I can just reflash old system image if it doesn't work .
How does ADB work for you on the AOSP treble rom?
Really_Rekt said:
How does ADB work for you on the AOSP treble rom?
Click to expand...
Click to collapse
Just tested it... I don't seem to be able to get it to work. :/ I don't know what the issue is either...
Hi,
currently i have installed RRR from OpenKirin (https://forum.xda-developers.com/honor-9/development/rom-t3754856) with magisk. But i think this ROM isn't updated anymore.
My question is: Can i install Treble Roms directly over OpenKirins ROM?
---------- Post added at 09:37 ---------- Previous post was at 09:31 ----------
Really_Rekt said:
How does ADB work for you on the AOSP treble rom?
Click to expand...
Click to collapse
Hi,
there are problems with magisk and adp: https://forum.xda-developers.com/showpost.php?p=76777735&postcount=282.
Saftpresse99 said:
Hi,
currently i have installed RRR from OpenKirin (https://forum.xda-developers.com/honor-9/development/rom-t3754856) with magisk. But i think this ROM isn't updated anymore.
My question is: Can i install Treble Roms directly over OpenKirins ROM?
---------- Post added at 09:37 ---------- Previous post was at 09:31 ----------
Hi,
there are problems with magisk and adp: https://forum.xda-developers.com/showpost.php?p=76777735&postcount=282.
Click to expand...
Click to collapse
Yes, you can flash it on top of any Project Treble (Oreo) Rom or EMUI 8 (Oreo) using my guide.
Magisk is kind of working for me although it crashes quite often and I have to reinstall the Manager or reflash it entirely fron time to time.
_lucx_ said:
Yes, you can flash it on top of any Project Treble (Oreo) Rom or EMUI 8 (Oreo) using my guide.
Magisk is kind of working for me although it crashes quite often and I have to reinstall the Manager or reflash it entirely fron time to time.
Click to expand...
Click to collapse
Thank you.
I read about problems with magisk and phhusson's gsi roms. I think to uninstall magisk before installing. I flashed magisk with fastboot, because i'm on stock recovery. So i have to read howto unroot with fastboot before i update.
_lucx_ said:
Just tested it... I don't seem to be able to get it to work. :/ I don't know what the issue is either...
Click to expand...
Click to collapse
The issue is talked about on PHH threads, it's caused by Magisk.
_lucx_ said:
Look at the bug list of each rom. As I said, I'm not the developer of any of those roms.
But I'm using the pure AOSP rom by phhusson and it's working perfectly fine without any issues as far as I can tell.
Click to expand...
Click to collapse
May I ask you how battery lie is, on AOSP?
enban said:
May I ask you how battery lie is, on AOSP?
Click to expand...
Click to collapse
Battery life was pretty good during my use without Xposed. I can't give you a specific battery life time now since I've installed Xposed which obviously made it a bit worse.
_lucx_ said:
Look at the bug list of each rom. As I said, I'm not the developer of any of those roms.
But I'm using the pure AOSP rom by phhusson and it's working perfectly fine without any issues as far as I can tell.
Click to expand...
Click to collapse
Hi,
I've several question for you :
1/ I wonder about security and privacy, do you think using aosp treble is better, than stock rom for that ?
2/ i don't care about gapps (gmail...), but i need the framework and google playstore.
If i take pure aosp without gapps does it have playstore and google frameworks ?
3/ which version do you use ? can you link me the version ?
Thanks.
Aqwel said:
Hi,
I've several question for you :
1/ I wonder about security and privacy, do you think using aosp treble is better, than stock rom for that ?
2/ i don't care about gapps (gmail...), but i need the framework and google playstore.
If i take pure aosp without gapps does it have playstore and google frameworks ?
3/ which version do you use ? can you link me the version ?
Thanks.
Click to expand...
Click to collapse
1. Well you kind of get a security risk anyway by unlocking the bootloader, rooting, etc. Other than that the Roms themselves are just what Android provides in terms of security.
2. No
3. for A-Only arm64 with Gapps and SU (https://forum.xda-developers.com/pr...development/experimental-phh-treble-t3709659)
_lucx_ said:
1. Well you kind of get a security risk anyway by unlocking the bootloader, rooting, etc. Other than that the Roms themselves are just what Android provides in terms of security.
2. No
3. for A-Only arm64 with Gapps and SU (https://forum.xda-developers.com/pr...development/experimental-phh-treble-t3709659)
Click to expand...
Click to collapse
Few questions for you buddy:
Does the camera work well?
Is fingerprint working well?
Do navkeys work?
I'm talking about aosp phh Treble.
And one thing, how to return to stock?
Extract system.img from stock rom with Huawei firmware extractor, flash it from fastboot like the aosp image, go to recovery and wipe cache and data, reboot and voila?
Double Chin Bigot said:
And one thing, how to return to stock?
Extract system.img from stock rom with Huawei firmware extractor, flash it from fastboot like the aosp image, go to recovery and wipe cache and data, reboot and voila?
Click to expand...
Click to collapse
Yes but you may use the os you had before flashing to treble, refer to https://forum.xda-developers.com/honor-9/help/help-to-stock-treble-custom-rom-t3804064
By the way thanks @_lucx_ for you answers
Double Chin Bigot said:
Few questions for you buddy:
Does the camera work well?
Is fingerprint working well?
Do navkeys work?
I'm talking about aosp phh Treble.
And one thing, how to return to stock?
Extract system.img from stock rom with Huawei firmware extractor, flash it from fastboot like the aosp image, go to recovery and wipe cache and data, reboot and voila?
Click to expand...
Click to collapse
- Yes 4K video is working (screen recording as well)
- Fingerprint is fully working with home button gestures set to Huawei's default for one button navigation - can be tweaked by editing the fingerprint.kl tho.
- Navbar is working fine for me but might have to do with the EMUI firmware you were on previously (although there's a fix for it now but I don't know if this fix works on Android 8.1)
_lucx_ said:
- Yes 4K video is working (screen recording as well)
- Fingerprint is fully working with home button gestures set to Huawei's default for one button navigation - can be tweaked by editing the fingerprint.kl tho.
- Navbar is working fine for me but might have to do with the EMUI firmware you were on previously (although there's a fix for it now but I don't know if this fix works on Android 8.1)
Click to expand...
Click to collapse
I think there's a misunderstanding. I was talking about the physical navigation keys (the ones near the fp sensor). Do they work as intended? Is it possible to deactivate the on screen navigation keys without root(because I want only the aosp Rom without anything else added)?
Today I flashed Pixel Experience GSI on my whyred after much trouble so here is a guide to make things clear.
if you are coming from MIUI you have to format data from twrp. this is a must to disable encryption.
after you are done formatting data. just do factory reset from twrp and then go to advanced wipe and then do the regular dalvik, cache, system, data and then swipe to wipe.
now the thing is whyred officially supports treble but the implementation is shoddy according to XDA folks. so if you flash GSI over miui's vendor there will be many bugs. like brightness slider not working and many things. so they(all credit goes to them) created a vendor zip which makes things really good. there are no bugs and it also supports volte. here is the download link .
https://www.androidfilehost.com/?w=files&flid=273660
now flash this zip file in twrp.
after that download the GSI of your choice from here.
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
remember to download arm64 A only system image.
here is pixel experience GSI which I prefer:
https://download.pixelexperience.org/treble_gsi/
now extract the zip and you will get a single .IMG file which is your system image. now go to twrp and then go to install then go to select install image downward. (don't flash directly, it's an .IMG file) then select the extracted .IMG file and then choose system and then flash.
then reboot system. that's it. you should boot fine.
download latest official twrp from here: https://dl.twrp.me/whyred
if you want root you will have to flash magisk beta 16.6 which works better on GSI. download here.
https://github.com/topjohnwu/Magisk/releases/download/v16.6/Magisk-v16.6.zip
to use Google camera you will have to enable camera2api. arnova's gcam doesn't work on this build. you will have to use BSG's gcam. here is the link. enable nexus style and active portrait mode from settings.
https://www.celsoazevedo.com/files/android/google-camera/f/MGC_5.2.022.apk
few tips: if your device is not booting and going to fastboot, flash magisk. it will definitely boot up.
if your device shows decryption failed, just format data from twrp. it will delete all user data btw.
no need to flash lazyflasher.
there are no uncertified device pop up from Google. so no need to worry.
playstore shows uncertified btw and magisk shows CTS false.
all the links that I have linked here, the credit goes to the creators. I am a normal user of XDA. thanks to them.
happy flashing and all hail the XDA lords.
How is Pixel experience gsi though?....faced any bugs till now?
it's good but there where few bugs. anyway pixel experience rom specifically for whyred has been released. you can flash that. it's great and bug free. download it here. it's not GSI though. normal ROM.
https://download.pixelexperience.org/whyred/
mr._.nobody said:
How is Pixel experience gsi though?....faced any bugs till now?
Click to expand...
Click to collapse
mr._.nobody said:
How is Pixel experience gsi though?....faced any bugs till now?
Click to expand...
Click to collapse
I was on the June build, I had issues with bluetooth audio (didn't work) and USB connection to computer (did not work). I think the USB issue was due to Magisk but I never did figure out the bluetooth issue.
No issues with the whyred version of Pixel Experience.
I also faced the same issue. But I see July build of GSI is up so those bugs might be fixed. anyway the PE ROM for whyred is excellent.
btw GSI will help us when P will release next month.
goofball2k said:
I was on the June build, I had issues with bluetooth audio (didn't work) and USB connection to computer (did not work). I think the USB issue was due to Magisk but I never did figure out the bluetooth issue.
No issues with the whyred version of Pixel Experience.
Click to expand...
Click to collapse
mearjunsha said:
I also faced the same issue. But I see July build of GSI is up so those bugs might be fixed. anyway the PE ROM for whyred is excellent.
btw GSI will help us when P will release next month.
Click to expand...
Click to collapse
So should I flash the ROM or the gsi?....are there any differences?
you should flash the ROM as it's specifically for whyred. its flashing instruction is different than GSI. but easy. just wipe and then flash the ROM. and reboot. that's it.
you may have to format data to disable encryption.
here is the forum discussion: https://forum.xda-developers.com/redmi-note-5-pro/development/rom-pixel-experience-t3816099
mr._.nobody said:
So should I flash the ROM or the gsi?....are there any differences?
Click to expand...
Click to collapse
Thanks mate for your experience, no detailed information in PE thread about wipes to do, before or after, can help with it? May be also with magisk release to install and best gcam to use?
remove all security like fingerprint, pattern etc.
go to twrp
go to wipe
do factory reset
go to advanced wipe
select dalvik, cache, system and data and then wipe
go to install
flash the pixel experience rom
reboot to system
that's it
if you get a prompt to enter password to start android then you will have to go back to twrp and go to wipe and format data and type yes. it will delete all your files btw. so backup everything. then reboot it will boot up fine.
after you have done booting and set up, go back to twrp and flash magisk v16. reboot to system. all done.
I have already given details of gcam in my OP. Kindly check that. The same works great on this ROM.
ask me if you face any problem. happy to help ?
trazalca said:
Thanks mate for your experience, no detailed information in PE thread about wipes to do, before or after, can help with it? May be also with magisk release to install and best gcam to use?
Click to expand...
Click to collapse
You are the man!!! 10 hours remaining for unlock bootloader, i'm ready and now, with your help, more confident... Thanks a lot!!
I understand your excitement but do check your build whether you are on Anti rollback. if you are on 9.5.19 you should absolutely not proceed right now.
read about it on XDA.
trazalca said:
You are the man!!! 10 hours remaining for unlock bootloader, i'm ready and now, with your help, more confident... Thanks a lot!!
Click to expand...
Click to collapse
I'm on global 9.5.6... never used phone and upgraded, i think that i can do it, i'm wrong?
you can go ahead. happy flashing! ?
trazalca said:
I'm on global 9.5.6... never used phone and upgraded, i think that i can do it, i'm wrong?
Click to expand...
Click to collapse
[dupe sorry]
You should by all means read about antirollback to be sure, but my understanding is that the antirollback refers to the firmware, not the rom. MIUI roms all include different firmware, so you can't rollback a MIUI rom (unless it's been modded to be firmwareless). But as far as I know, no custom roms include firmware, so you should be fine even if your firmware is ARB triggered if all you're doing is installing custom roms.
Hi, someone flashed latest Pie Phh GSI? I tried with PE CAF, AOSIP, and Mokee vendors but doesn't boot, always stuck at the Mi logo, even I flashed the permissiver patch without luck.
Is GSI better than respective Rom (say Havoc GSI as compared to Havoc OS rom)?
ShadowFax said:
Is GSI better than respective Rom (say Havoc GSI as compared to Havoc OS rom)?
Click to expand...
Click to collapse
Nope.
Hello Android community ....
I have a problem with my rooted OP6.
I always use my devices with root but since model OP6 I'm too stupid for that or have not found any suitable instructions?
I root and install the TWRP on the OP6
then I install the original FULLROM followed by the current and matching MAGISK to get root
and it boots perfectly including root and everything is great!
but the TWRP is always gone ...
that makes me totally crazy
What am I doing wrong or what can/must do differently so that the TWRP recovery stays on for the next time?
Does anyone have a tip for me?
Many Thanks
VG
Z.
This is how you do it from twrp.
Flash rom (DON'T REBOOT)
Flash twrp (now reboot to recovery)
Flash magisk and boot = done.
Full roms will write over partitions.
whizeguy said:
This is how you do it from twrp.
Flash rom (DON'T REBOOT)
Flash twrp (now reboot to recovery)
Flash magisk and boot = done.
Full roms will write over partitions.
Click to expand...
Click to collapse
Thanks - maybe this also helps to resolve one of my confusions: will this now also work with Standard (not BluSpark) TWRP and Android Pie - there's all kinds of mixed statements online. Best
CoffeeMachineSwitch said:
Thanks - maybe this also helps to resolve one of my confusions: will this now also work with Standard (not BluSpark) TWRP and Android Pie - there's all kinds of mixed statements online. Best
Click to expand...
Click to collapse
I always use blu-spark. Always work
whizeguy said:
I always use blu-spark. Always work
Click to expand...
Click to collapse
thanks - but isn't that another source of complexity and error, as another party (bluSpark developer) is involved on top of TWRP team? And Magisk. Seems like many cooks throwing in ingredients to root, while the Android system itself keeps updating and changing....
People need to learn to READ
Hi all,
I'm presenting here my ROM for S10e (whose main thread is https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915 ).
It is generic, but it doesn't mean anything bad!
Pretty much every works, and this is my daily driver (Exynos variant).
What works:
- Camera
- Wifi
- 2G/3G/4G, including signal level
- Phone calls
- Fingerprint sensor
- Encryption
- Proximity sensor
What doesn't work
- VoLTE
- stock OneUI camera app
- MTP
You can install some modded Google Camera on it for acceptable Camera quality.
Download links:
- With included gapps
- Without included gapps
How to flash:
- Flash back latest stock ROM
- Extract the img.xz into .img
- Flash it to system partition using Heimdall: https://glassechidna.com.au/heimdall/
- Flash this to vbmeta partition https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img (also using Heimdall)
- Boot once. The device will reboot into recovery, that's okay! Just do a factory reset and boot to system again.
- If it didn't reboot into recovery on its own, that's not normal (perhas you have magisk installed?), but still reboot into recovery and do a factory reset.
- Enjoy!
Recommended after installing:
- Default Launcher is AOSP's. It sucks. You should really install another Launcher. I recommend and use Lawnchair
- Pretty much no Google app is preinstalled, only Play Store and Chrome. You'll probably want to install Google, Google Assistant apps, Gmail, ...
free post for me and myself
Support for G9700?
Could system.img possibly be flashed through recovery? And you could've made it a flashable zip, we have a pretty ok recovery when you flash multidisabler
DeHuMaNiZeD said:
Could system.img possibly be flashed through recovery?
Click to expand...
Click to collapse
Yes
And you could've made it a flashable zip, we have a pretty ok recovery when you flash multidisabler
Click to expand...
Click to collapse
TBH I recommend not to flash any disabler, they bring more issues than they fix.
Android security is already not ideal, disabling encryption sounds like a very bad idea
(And disabling dm-verity is totally useless, because when flashing a GSI it already is)
NisseGurra said:
Support for G9700?
Click to expand...
Click to collapse
Yes G9700 is supported, though bear in mind that since it's not the same device, you don't really have the same guarantees. I'll help you through your issues either way.
Ok, tested on G9700, latest stock rom installed (android 9).
TWRP with multidisabler installed, format data, reboot recovery. Install V120 gsi, reboot.
Boots nicely.
Findings: no autobrightness, slider ok tho. Wifi/BT/NFC ok. No MTP (as stated)
Dual sim ok, voice calls ok, data ok. 3.5 output ok
Edit: Best way to root?, addonsu-16.0-arm64-signed.zip?
im gonna try this right away
i have one simple question before trying does magisk work with this and can i just use a magisk pachted system
---------- Post added at 07:32 AM ---------- Previous post was at 07:16 AM ----------
To my knowledge s10e is A-only and you linked A/B. What's up with that?
Edit:// It seems it is not, I have no idea why treble testing app from app store does not detect, that it is A/B
mikk150 said:
To my knowledge s10e is A-only and you linked A/B. What's up with that?
Edit:// It seems it is not, I have no idea why treble testing app from app store does not detect, that it is A/B
Click to expand...
Click to collapse
In the true sense, it is A-only, it doesn't have seamless update.
The difference between A-only and A/B was that A/B included the init, while A-only didn't.
But since Pie, A-only also includes init, like A/B. I didn't update the naming convention (because it just gets even messier).
Hackintosh5 developed Treble Info ( https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=en_US ) to make things clearer.
Do you have PHH for Android 10 for this device?
vlubosh said:
Do you have PHH for Android 10 for this device?
Click to expand...
Click to collapse
It is still unstable, that's why I haven't shown it in this forum yet.
Do these steps apply to any devices? Or only specific models? I have an Elephone Soldier, and I notice different website have different procedures. Not sure which one is right. Thanks.
"How to flash:
- Flash back latest stock ROM
- Extract the img.xz into .img
- Flash it to system partition using Heimdall: https://glassechidna.com.au/heimdall/
- Flash this to vbmeta partition https://dl.google.com/developers/and...gsi/vbmeta.img (also using Heimdall)
- Boot once. The device will reboot into recovery, that's okay! Just do a factory reset and boot to system again.
- If it didn't reboot into recovery on its own, that's not normal (perhas you have magisk installed?), but still reboot into recovery and do a factory reset."
I just installed AOSP 9.0 v119 for my Elephone Soldier. I can confirm the system boots up, but there is no sound. (ie. ring tone, media, notification) None of these sound work.
One question guys. If i root my s10e and flash custom rom, and then if i want to back to full 100% stock rom, o just need to flash it with odin and everything will be same like before? All apps will work like samsung health and pay? Thanks
BratoMo225 said:
One question guys. If i root my s10e and flash custom rom, and then if i want to back to full 100% stock rom, o just need to flash it with odin and everything will be same like before? All apps will work like samsung health and pay? Thanks
Click to expand...
Click to collapse
No as I have heard. The knox fuse is a physical fuse which can never be reset so these apps will not work.