Related
Has anyone managed to get it working? I just tried to install via FlashFire and wound up getting an animation loop on the SlimLP boot logo. I applied the 5.1.1 firmware through the "apply update through adb" option in the recovery, can anyone confirm Xposed even working on SlimLP?
I'd like to know this also. Have not tried it yet.
I think you have to use the slim-rom version from the 4th post. The original slim rom is not running with xposed beacause of some ART optimizations... Read the slim rom thread. There you can find something about it.
Thanks! Think I found an easier solution than installing Xposed for what zip needed though (just needed YouTube to play in the background). That will come in handy if I want it later for any reason though.
Yes, xposed works fine. Big thanks to csolanol!
You must use the xposed compatible SlimLP 0.13 build + the correct xposed version (see the howto xposed thread in Fire General forum).
Anybody had success with getting .013 build running successfully with eXposed.. I've tried the ' Slim-ford-5.1.1.beta.0.13-UNOFFICIAL-20151221-0949.zip ' build from root junkies tutorial i think in section 4 or something if i remember vaguely, but with no luck... The Flash just proceeds as expected then reboots while opening/loading .zip.. But the standard release 'non-eXposed' runs without any problems.
Need to include more information. You're flashing with twrp or flashfire? If you used flashfire, what are you coming from? Stock 5.1.1 or another rom.
Do you mean after flashing the rom your Fire will not boot / start up?
I flashed SlimLP 0.13 via twrp without a problem on two different Fires. Xposed runs fine.
thanks for your reply, I'm flashing with flashFire from a r00ted fresh clean stock fire-os 5.1.1 on Amazon Fire 7" 5th Gen. i execute flash after selecting wipe all partitions except sd and then load .zip via ota then push button to commence flash, it proceeds to blank screen and then flashing screen and begins to attempt rom install i see rom info and 'char pic' of rom then it self terminates and reboots to existing r00ted fire-os, i do this exact same process with the rom not currently supporting Xposed from rootjunkie download site, and everything completes successfully spending a slightly longer period at the rom install/upload stage completing successfully with slimlp running nice... minus a few almost irrelevant bugs i noticed...
Twrp via adb doesn't work with 5.1.1 right? only works on 5.0.1&2? .. unless im mistaken.. any ideas?
Yep, we can't use twrp on 5.1.1.
So you select to wipe, system data, 3rd party apps, dalvik cache, cache partition, correct? I'm afraid I have no suggestions.
exactly that's correct , then i select rom, then i select gapps. then press flash button and it halts on the next screen as it begins to flash rom and quits to a reboot .. everything still unchanged as it was.. i have tried this process installing from stock os fire 5.1.1 & slimlp 5.1.1 with unsuccessful results.. but hey at least i have a SlimLp non-Xposed edition installed that beats Fire-BS#"*t any day. guess I'll have to wait for a new build to be released. bummer.
---------- Post added at 12:32 ---------- Previous post was at 12:25 ----------
in the future i guess more concentration is needed on the 5.1.1 Xposed edition skimlp rom to be flashed from 5.1.1 stock, for the true android custom eXperience .. i have also seen a fw roll back to 5.0.1or5.0.2 is not possible from any 5.1.1 os. never mind.
What I find is odd is that you've selected to wipe first. Flashfire should be wiping before trying & failing to flash SlimLP 0.13, leaving your Fire wiped & unable to boot back into the stock FireOS (you would then need to restore FireOS 5.1.1 via adb sideload in the amazon recovery). FlashFire is in beta & I think it's currently a bit buggy.
Bib_x said:
I think you have to use the slim-rom version from the 4th post. The original slim rom is not running with xposed beacause of some ART optimizations... Read the slim rom thread. There you can find something about it.
Click to expand...
Click to collapse
Sorry, I feel I joined the conversation mid-way but, which SlimROM thread are you talking about?
There is only one SlimLP-Thread in android development section.
Newest SLim-Version for Fire is without Art-Optimizations, so you can use xposed now with the latest slimlp 0.14.
With the older SlimLP 2.3 there was Art-Optimization inside - so there no xposed was working.
Bib_x said:
There is only one SlimLP-Thread in android development section.
Newest SLim-Version for Fire is without Art-Optimizations, so you can use xposed now with the latest slimlp 0.14.
With the older SlimLP 2.3 there was Art-Optimization inside - so there no xposed was working.
Click to expand...
Click to collapse
Thanks for the reply. I actually don't have a Fire and came across this thread after a lot of googling. I'm running SlimLP 0.12 I think on a Note Edge. I absolutely love this ROM. Seriously, I was close to selling the phone for scraps until I flashed this ROM. Now I think I will never buy another phone unless there is SlimROM support already
Anyway, I've been looking everywhere for a solution to get Xposed running. I found people saying that SELinux needs to be set to Permissive which I have done but still no luck. Are you saying that it's impossible with SlimLP versions before 0.14? Somehow, I doubt that would come to the Note Edge
marcolorenzo said:
Thanks for the reply. I actually don't have a Fire and came across this thread after a lot of googling. I'm running SlimLP 0.12 I think on a Note Edge. I absolutely love this ROM. Seriously, I was close to selling the phone for scraps until I flashed this ROM. Now I think I will never buy another phone unless there is SlimROM support already
Anyway, I've been looking everywhere for a solution to get Xposed running. I found people saying that SELinux needs to be set to Permissive which I have done but still no luck. Are you saying that it's impossible with SlimLP versions before 0.14? Somehow, I doubt that would come to the Note Edge
Click to expand...
Click to collapse
Maybe try looking in the Note Edge forum not the Amazon Fire one?
Pond-life said:
Maybe try looking in the Note Edge forum not the Amazon Fire one?
Click to expand...
Click to collapse
Maybe you shouldn't presume, with no information, that people are imbeciles? Don't you think I would've have done that at the beginning? Anyway, I may be wrong but I presumed that whether or not Xposed worked was more dependent on the ROM and not the phone? So if people here, who are discussing Xposed on SlimROM can help me, why not ask?
Bib_x is correct, i confirm Xposed working on slimlp build 0.14 beautifully for Fire 7 5th Gen.. be wary of modules you install other wise you'll have to start everything from scratch when you reach a boot hang because of a not yet compatible module.. you have no custom recovery remember so no quick fix, can always fresh install everything lol., which is good training lol.
This thread is for people that want a faster and more reliable method to get root/custom recovery and viper and Xposed plus debloating your device and not having to go through countless other threads to find files
I am not held responsible if you miss read and screw up your phone<----extremely hard to do with this method but if anything does happen either load your backup you make or just plug in your phone to kies and firmware update your phone it will bring your phone to stock firmware no root no custom recovery then you can restart
(sm-g903F and Canadian variants are also know as the Samsung galaxy s5 neo)<------ I know there different variants but this is for SM-G903F and Canadian variants ONLY
I will have all the file you need for everything you need
if its not a dropbox link it will be a play store link
ROOT
https://www.dropbox.com/s/pz8x0wj4f6okjdg/CF-Auto-Root-s5neolte-s5neoltexx-smg903f.zip?dl=0
make sure you have ------>(OEM UNLOCKED)<------MOST IMPORTANT,unknown sources, USB debugging all enabled or you will go into a bootloop or soft-brick
flash this with ODIN everything should work fine
TWRP RECOVERY
as of right now that I know of the neo does not have a working CWM recovery soo TWRP will have to do
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
(when in the app look for this name Samsung Galaxy S5 Neo Exynos flash that one in the app and you should be good)
Viper4Android 5.1.1(audio mod)
(all of these are flashed in recovery EXCEPT for the presets you put those in the viper4android folder for presets that is created after you install the app it should be in your sdcard directory near the bottom)
please flash V4A2.3.4.0 then policy fix you should then be able to install the audio driver (use super high quality<----the best sound ) inside the viper app. then go to the settings tab and update the app.....
if when you install the new version viper stops working and there is no sound or it asks you to install the driver again please go and re-flash the policy fix then go install the driver
(viper4android 5.1.1)
https://www.dropbox.com/s/1grrl3yhghc8o2n/V4A2.3.4.0_Lollipop.zip?dl=0
im pretty sure this is the right policy file what it does is allows stuff like xposed framework and viper to run with SELinux set to enforcing
if you guys have problems just comments and ill fix anything
(policy fix)
https://www.dropbox.com/s/1pj5u0g5k7db6n7/ViPER4Android-supolicy.zip?dl=0
(Viper profiles)
https://www.dropbox.com/s/shfdoqvq1ioiejq/eXtremeBeats%20Viper%20Presets%20v1.0.zip?dl=0
XPOSED
(make sure you have ran the policy fix from the viper4android)
this is for stock or close to stock roms only!!!!!!
1.Install Xposed Installer App
Xposed installer App
2.Make a backup not needed but always helpful
3.Copy the Xposed file and the uninstaller to your sdcard
xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip (XPOSED FRAMEWORK FILE)
EXPOSED UNISTALLER FILE
4. Flash "xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip"<---- Xposed FrameWork File) through TWRP recovery this is the one for our SM-G903F and Canadian variants that are running 5.1.1
if anyone has ARM64 system on 5.1.1 or 6.0.0 orrrrrr this phone with 6.0.0 contact me and ill put thoses files up as well
- ARM means the devices that are running arm32 operating system (Galaxy S5, Note4,...)
- ARM64 means the devices that are running arm64 operating system (Galaxy S6, Note5 and all their variants...)
- SDK22 means Android Lollipop 5.1.x
- SDK23 means Android Marshmallow 6.0.x
DEBLOATING&Disable annoying "Check battery cover"
for debloating just download this and flash with recovery and bam!!!!! done :good:
for Disable annoying "Check battery cover
just go into rom toolbox or anyapp that you can see system app and freeze or disable this apk "Popupuireceiver.apk"
Credits
Chainfire for root
twrp for recovery
wanam for xposed
ViPER's Audio founded by ViPER520.
Co-founded by ZhuHang.
CN. vipersaudio.com / EN. facebook.com/vipersaudio
Copyright (C) 2006-2016 vipercn.com / vipersaudio.com
FOR THE AMAZING VIPER4ANDROID
Nice which apps or data's will be all debloated by this file
LetMeShow said:
Nice which apps or data's will be all debloated by this file
Click to expand...
Click to collapse
ill have to get back to you on that I have the list but I may be merging with another thread soooo ill keep updated
I'll possibly will be merging with another thread but all this info is working
(make sure you have ------>(OEM UNLOCKED)<------MOST IMPORTANT) meaning I have to have an unlocked phone?
@adbpusher123: Thread merged. If anything needs to be changed, tell me
Thanks.
RE: Galaxy S5 Neo SM-G903W help question
[SIZE="7" said:
XPOSED[/SIZE]
(make sure you have ran the policy fix from the viper4android)
this is for stock or close to stock roms only!!!!!!
1.Install Xposed Installer App
2.Make a backup not needed but always helpful
3.Copy the Xposed file and the uninstaller to your sdcard
4. Flash "xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip"<---- Xposed FrameWork File) through TWRP recovery this is the one for our SM-G903F and Canadian variants that are running 5.1.1
if anyone has ARM64 system on 5.1.1 or 6.0.0 orrrrrr this phone with 6.0.0 contact me and ill put thoses files up as well
- ARM means the devices that are running arm32 operating system (Galaxy S5, Note4,...)
- ARM64 means the devices that are running arm64 operating system (Galaxy S6, Note5 and all their variants...)
- SDK22 means Android Lollipop 5.1.x
- SDK23 means Android Marshmallow 6.0.x
Click to expand...
Click to collapse
Hi I was going to try to install Xposed on a Samsung Galaxy S5 Neo Canadian variant (SM-g903W).
I'm currently rooted running marshmallow 6.0.1 with TWRP installed.
If I'm correct you have a specific installer for the marshmallow set up? please let me know.
Thanks
Are there any current roms available for the 903w (canadian version)?? Also can other 903neo roms be applied to it?
SH-G903W FRP - cannot get past verification
Hi I have a Samsung Galaxy 5 Neo Rogers Canada I cant seem to get past the FRP. I have tried to bypass it using an OTG Cable on a USB drive with the .APK to bypass. My issue is , when I connect the USB the drop down menu on the phone does not appear. I am assuming this is because the phone has the latest software installed onto it since the patch in Jan 2015. In order for me to install another version of OS i need to be able to turn on USB Debugging and Dev or I may soft brick the phone ? correct ?
in other videos online once the usb OTG cabel is connected a popdown menu lets you install the apk. I cannot get that menu to pop down.
So I am guessing my best bet would to be to revert to a version before the patch. Which I am having a hell of a time finding. I am very unsure If i can even load another OS without being able activate the Debug or Dev.
Can anyone help ? Im not sure what else to do.
also i appologive if this post is in the wrong directory
[email protected]
---------- Post added at 06:02 AM ---------- Previous post was at 05:46 AM ----------
I also just tried SlideSync and it looked very promising. Again, no pop up window when connected. Getting very frustrated. lol. please help.
gunsum said:
Hi I have a Samsung Galaxy 5 Neo Rogers Canada I cant seem to get past the FRP. I have tried to bypass it using an OTG Cable on a USB drive with the .APK to bypass. My issue is , when I connect the USB the drop down menu on the phone does not appear. I am assuming this is because the phone has the latest software installed onto it since the patch in Jan 2015. In order for me to install another version of OS i need to be able to turn on USB Debugging and Dev or I may soft brick the phone ? correct ?
in other videos online once the usb OTG cabel is connected a popdown menu lets you install the apk. I cannot get that menu to pop down.
So I am guessing my best bet would to be to revert to a version before the patch. Which I am having a hell of a time finding. I am very unsure If i can even load another OS without being able activate the Debug or Dev.
Can anyone help ? Im not sure what else to do.
also i appologive if this post is in the wrong directory
[email protected]
Click to expand...
Click to collapse
I just did my S5 Neo SM-G903W.
Follow the instructions for the 2nd option: 2. Bypass any Samsung Galaxy Google Account Verification without OTG
Once you've done that you have to make sure when using Odin that auto reboot is "unchecked" or it will boot into the oem recovery and not TWRP.
So once Odin gives you a successful pass, close it. Turn your phone off by pressing both volume keys + home + power key and it will shut off in a few seconds.
Then boot into TWRP by holding the Vol up key + home + power
However, there are no custom roms for the Neo, and the ones for the S5 (900 series) won't work; I tried.
Got it!
Thanks for your reply man I didn't think I was going to get any help on this. I actually did end up figuring this out I used a USB drive that had a light in it this way I could tell when the disc was being read I was simply being too impatient and not letting the disc read. I waited a few moments sure enough the menu popped up so I could go into settings using the APK. So all-in-all I did learn my lesson to be more patient , also to use a drive that had a light inside of it. However after I did get into the phone and put a SIM card in it said not registered on network.
Glad you got it working.
I have my S5Neo rooted by using SuperSU once I got TWRP installed.
So there's no custom roms which kinda sux, but at least with a rooted phone you can install great rooted apps: enhance the sound with Viper4 FX etc etc
And there is the bloatware remover.
Lot's of other great stuff on xda.
Standard Disclaimer:
I am not responsible for anything that may happen to your device.
With that being said, I will keep this thread updated as long as i can.
These are Verizon HTC 10 Stock, Deodexed, Completely Stock (all bloat included) bases. They are pre-rooted with whatever magisk version was available at the time. They are a free-for-all, use them however you wish.
3.18.605.13
https://www.androidfilehost.com/?fid=890129502657598174 MD5 c97a4c93df3da25e1f22cd1127d849b8
2.41.605.36
https://www.androidfilehost.com/?fid=673791459329069570 MD5 7cce84219e1b303756b19bafbe7b783d
2.41.605.30
https://www.androidfilehost.com/?fid=673791459329060279 MD5 d291ff5fc4d976945c9aea049f17d614
2.41.605.23
https://www.androidfilehost.com/?fid=673791459329049102 MD5 efa87895b1d1dbe7fc02a8d9431149dc
2.41.605.20
https://www.androidfilehost.com/?fid=961840155545587464 MD5 09113483aaedcf51c0ac285007d50f5d
2.41.605.18
https://www.androidfilehost.com/?fid=817550096634772248 MD5 404ada2b1c2aa8bdfbff0f240fa39264
Installation Instructions:
Please Note: You must be S-OFF | Bootloader locked/unlocked with TWRP
1. Download ROM and confirm MD5 matches, pasted for your convenience.
2. Flash/be running current/latest/matching firmware. Download from here.
2A. Alternatively, you can flash the RUU, and get the same result. Download from here.
3. Download/Install/Flash Latest TWRP Recovery (If TWRP is not already installed)
3A. Reboot into Recovery.
4. Full Wipe: Dalvik Cache, Cache, Data, System.
5. Install ROM.
6. Reboot, the initial boot will be awhile optimizing (Anywhere from 5-15 minutes realistically).
Thanks:
HTC
dottat - RUU's used for base, help
kisakuku - RUU's used for base currently
Santod040 - Nougat firmware, help
andybones - Lots of help from him
buckmarble - Lots of help from him
SuperR - SuperR Kitchen
topjohnwu - Magisk
leedroid - figuring out the nuances of oreo
XDA:DevDB Information
Verizon HTC 10 Stock Deodex Bases, ROM for the Verizon HTC 10
Contributors
aer0zer0
Source Code: http://dl4.htc.com/RomCode/Source_and_Binaries/perfumewlvzw-3.18.31-perf-g4f98addbcf4.tar.gz
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Based On: RUU Source
Version Information
Status: Stable
Created 2017-11-10
Last Updated 2017-11-10
Installation Instructions/Nuances of Oreo
Deodexing Oreo is a little bit janky. The boot.img need to be patched to allow for use of dalvik cache, or it is really really slow.
Installation of the deodex base for the first couple of reboots is pretty odd
1. Install it as you would any other base.
2. When it reboots, the screen will stay black for 10-15 minutes (crack a beer and wait, dont worry)
3. Once it boots, it may or may not throw a systemui error, press wait and continue with the initial setup and get into the OS
4. reboot once or twice, and the speed shall return.
Reserved
It says 404 error not found for the newest rom .30
Codyl10 said:
It says 404 error not found for the newest rom .30
Click to expand...
Click to collapse
fixed, thank you for telling me, i appended an extra https:// to the front end
2.41.605.36 is Up
aer0zer0 said:
2.41.605.36 is Up
Click to expand...
Click to collapse
@hgoldner does magisk 15 work on the 10? I'm in essential Neverland now. Haven't played with my 10 in weeks....really should
aer0zer0 said:
@hgoldner does magisk 15 work on the 10? I'm in essential Neverland now. Haven't played with my 10 in weeks....really should
Click to expand...
Click to collapse
Absolutely. Have Stock Verizon 2.41.605.36 running with Magisk 15 on my 10. Typically I roll back to the stock recovery and boot images, take the OTA, then reflash TWRP, then Magisk, then ElementalX kernel.
And I still prefer my 10 to the U11 (and I detest Oreo).
hgoldner said:
Absolutely. Have Stock Verizon 2.41.605.36 running with Magisk 15 on my 10. Typically I roll back to the stock recovery and boot images, take the OTA, then reflash TWRP, then Magisk, then ElementalX kernel.
And I still prefer my 10 to the U11 (and I detest Oreo).
Click to expand...
Click to collapse
Really liking the essential phone. Engineers are fairly regular on Reddit, lots of stuff going on
aer0zer0 said:
Really liking the essential phone. Engineers are fairly regular on Reddit, lots of stuff going on
Click to expand...
Click to collapse
But no removable storage and no Verizon so no deal here.
hgoldner said:
But no removable storage and no Verizon so no deal here.
Click to expand...
Click to collapse
Verizon works perfect actually. LTE/3G/1X HD calling/VOLTE. Only thing your missing out on is video calling/wifi calling. No external sd is troublesome, but I have made it work. Super easy to flash thing. A/B is still kinda new, especially coming from HTC. Very enjoyable experience for me so far
ALSO: to note: they freely give away betas to anybody who wants to test and report bugs. Its not the gift of the select few like like the 10 (huddled around a flickering fire, waiting for @santod040 @hgoldner @dottat to throw them bone of what is next to come) over dramatic...lol but seriously i really like the concept, fairly transparent. They want you to be their dev base
OP and 2nd Post Updated. Added the Oreo Deodex Base.
Hi there. I have the UK varient which is not the same as the us version. I'm looking for info regarding root and custom roms. All info I can find points toward the us (James) varient.
Any info or links greatly appreciated
ok so update, found this thread but not sure if the information is correct, thoughts or experiences please
https://forum.xda-developers.com/moto-e5/how-to/moto-e5-xt1920-15-pettyl-unlock-t3859586
mac_d4di said:
ok so update, found this thread but not sure if the information is correct, thoughts or experiences please
https://forum.xda-developers.com/moto-e5/how-to/moto-e5-xt1920-15-pettyl-unlock-t3859586
Click to expand...
Click to collapse
That's my thread and yes the information is correct.
If you are not sure yourself that the information I have posted is correct, then I suggest you stop thinking about rooting your E5 or flashing custom ROMs.
You have to remember no one has tested the rooting/flashing procedures on PETTYL.
Everything that's listed here on XDA is designed for James/Nora/Hanna devices so no one has tested anything on our devices as it's newer and not many have it.
All the GSIs (custom ROMs) are only listed as working on the James/Nora/Hanna devices, there is currently no support offered for PETTYL, although technically they should work.
The devs of those other devices and the resources for them claim everything should work on our E5 as its treble compatible, but unfortunately that's not quite correct.
If you are really not sure about anything, or don't know if information is correct, you will have problems.
Im not being mean.....I really don't want anyone else to have the problems I have had and really wouldn't advise anyone to go through the process as it's fraught with issues, bad explanations and lacking important information.
Some files are incorrect for our device and some listed procedures for the other devices do not work on our E5.
BTW-my device is an E5 play XT1920-15 PETTYL SIM unlocked purchased from Argos.
Here's a list of the issue I found, it might be different for someone else as two people are saying they successfully rooted their PETTYL, and I couldn't.......
1. I had no issues unlocking the bootloader.
2. There are two versions of TWRP posted on XDA for PETTYL, but neither worked for me.
I used the James version.
3. I could not root my device.
Magisk installed but I could not get v17.3 or v17.2 to flash.
V17.1 did flash but magisk manager showed device not rooted and magisk not installed.
4. Flashing any GSI (Oreo or Pie) causes problems to the system sounds, ringtones, notification tones and music which is totally distorted and very poor quality.
The camera has very poor quality as well.
5. Lineage OS 15.1 is the GO version, you also should flash lineage before flashing other GSIs as you can't flash most GSis over stock.
6. You can use the full Google apps on a couple of android 9 gsis which makes your device a normal android, not an android Go device, but I would recommend not to bother with Android 9.0 GSis for this device as they are very buggy and very slow, and they use three times more battery than android 8.1 Go.
Also, live wallpaper and notification access still don't work on android 9.
Just remember as well the US E5 is much more powerful than our E5, and I assume thats why android 9 runs so crap on our E5.
7. You have a very complicated process to get your Google account working on any GSI, if you do it wrong, you will not be able to use your Google account at all and will get spammed with never ending notification from Google of using an "uncertified device"
8. If you run into problems and decided to return to stock, you cannot download the "retail_GB" stock firmware (SIM unlocked) for PETTYL unless you pay for it....the EE and Tesco SIM locked firmware is free to download, but neither work on the SIM unlocked version if you use non EE or non Tesco SIM cards.
9. Someone has posted a twrp back up of rooted stick for PETTYL.
It did not boot on my device and just kept boot looping.
That could have been a twrp issue and nothing to do with the shared back up - I couldn't get back into a gsi or stock to test it.
My post is warning to other PETTYL users- with my own experience.
What you choose to do is up to you but I really would not bother tampering with it, leave it be.
Stock android Go 8.1 is way better than anything else that's currently available for PETTYL right now, every gsi I tried had an issue of some description that affected performance so badly they were practically unusable.
Even though I'm back on stock now I still have sound issues, and many graphic glitches that makes my screen flash and glitch out randomly.
I'm sorry it's such a long reply, I wanted to give you as much information as possible so you have some idea of what's involved for our device., And let's just hope the situation for our device will get better soon.
Thanks for your detailed reply, I only asked if this was correct as I was aware of the differences between models etc.
I wouldnt say im new to rooting cfw etc, I have been flashing phones since 2002 lol.
But I dont want to brick this device as its currently my only phone, so I will wait and see if the situation improves in the future.
Its not a bad phone as it is you get quite a lot of phone for £65 nowadays.
Oh and im using simlocked tesco model so free to download, I find it stupid that you have to pay for stock firmware its beyond belief
mac_d4di said:
Thanks for your detailed reply, I only asked if this was correct as I was aware of the differences between models etc.
I wouldnt say im new to rooting cfw etc, I have been flashing phones since 2002 lol.
But I dont want to brick this device as its currently my only phone, so I will wait and see if the situation improves in the future.
Its not a bad phone as it is you get quite a lot of phone for £65 nowadays.
Oh and im using simlocked tesco model so free to download, I find it stupid that you have to pay for stock firmware its beyond belief
Click to expand...
Click to collapse
Just like you, I've been rooting and flashing phones since like forever, and this device is the first I've ever had issues with.
It's entirety possible that as I'm a "noob" to flashing system images and fastboot flashing as apposed to flashing "ROMs" I may have messed up the procedures or made mistakes.
But not to be outdone, I have just before typing this reply tried again to root my E5 and flash a GSI, and again the process failed for me.
I could not boot into lineage OS 15.1 due to a "decryption error" and also couldn't get twrp to flash anything.
I've read now my issues are down to the DM Verity kernel which seems to be causing a lot of confusion amongst users and It now seems the process to remove forced encryption is what's causing all my issues.
I don't understand the process if I'm honest (it's an age thing lol) and worse, there is a lot of conflicting information, as a few people are saying the DM Verity process isn't necessary!!!
So unfortunately I've given up completely for now and stand by my original advice.
It's best to leave this particular device well alone until we have a proper procedure and tutorial in place for our own devices rather than trying to follow procedures for the US version.
I'm jealous though you only paid £65, as I paid £79.99, but I still think this Moto E is better than the Nokia 3 it replaced.
If any one can send me any issues they have with pettyl xt1920-15 rooting/twrp/etc I will try to test everything I can and see what works don't expect anything till January cause got college till the 23 and no time now
plscotland said:
If any one can send me any issues they have with pettyl xt1920-15 rooting/twrp/etc I will try to test everything I can and see what works don't expect anything till January cause got college till the 23 and no time now
Click to expand...
Click to collapse
That's very generous of you.
Like you, I don't get much time (due to work) but I have two weeks off from 21/12 and can supply as much information as you want.
I would like root if it's possible.
If some can check this twrp in fast boot by booting it and tell me dose it work on thier phone i be thankfull https://github.com/TwrpBuilderTests...s/tag/TWRP-3.2.3-TwrpBuilder-2018-10-28_04-33
plscotland said:
If some can check this twrp in fast boot by booting it and tell me dose it work on thier phone i be thankfull https://github.com/TwrpBuilderTests...s/tag/TWRP-3.2.3-TwrpBuilder-2018-10-28_04-33
Click to expand...
Click to collapse
I have a "working" 3.2.3 version for PETTYL but I'm not sure it's the version you linked
The one I have "works" in that it boots to TWRP fine from fastboot but obviously it doesn't flash.
I can't flash GSIs through that version, where they do flash no problems through fastboot......
Finally, I can flash magisk through that as even though magisk flashes successfully, magisk manager shows magisk is not installed and asks to flash it again.
@plscotland
TWRP - won't flash to recovery partition.
Cannot mount vendor to flash Fstab
Magisk flashes but magisk manager shows not installed.
I tried the twrp I sent you and the James version.
Lineage - I can successfully flash and boot lineage over stock (Phhusson version) but I have issues with "device not certified by Google" and get spammed by constant notification from Google
Cannot use for daily driver due to no nav bar orfind any settings to enable nav bar.
Descendants 1.0.5 - I have successfully flashed and booted this "rom" and used it but the sound from system ringtones and notification tones is awful and distorted
Lots of graphical glitches and system UI has stopped errors
Pixel experience - cannot flash - error whilst flashing that system IMG is bigger than target.
If I wipe data, it just bootloops and won't go past splash screen.
Resurrection remix - cannot boot
Bootleggers 3.0 - cannot boot
Hope some of this information helps you.
XT1920 - 15 retail GB firmware (SIM unlocked) stock android 8.1 go currently
bubba1601 said:
@plscotland
TWRP - won't flash to recovery partition.
Cannot mount vendor to flash Fstab
Magisk flashes but magisk manager shows not installed.
I tried the twrp I sent you and the James version.
Lineage - I can successfully flash and boot lineage over stock (Phhusson version) but I have issues with "device not certified by Google" and get spammed by constant notification from Google
Cannot use for daily driver due to no nav bar orfind any settings to enable nav bar.
Descendants 1.0.5 - I have successfully flashed and booted this "rom" and used it but the sound from system ringtones and notification tones is awful and distorted
Lots of graphical glitches and system UI has stopped errors
Pixel experience - cannot flash - error whilst flashing that system IMG is bigger than target.
If I wipe data, it just bootloops and won't go past splash screen.
Resurrection remix - cannot boot
Bootleggers 3.0 - cannot boot
Hope some of this information helps you.
XT1920 - 15 retail GB firmware (SIM unlocked) stock android 8.1 go currently
Click to expand...
Click to collapse
Thanks I check and send u how to boot resurrection remix later cause there are extra steps for it to work and fstab also has to be done in another way once IM off work I do a guide for it /Info helped a lot
plscotland said:
Thanks I check and send u how to boot resurrection remix later cause there are extra steps for it to work and fstab also has to be done in another way once IM off work I do a guide for it /Info helped a lot
Click to expand...
Click to collapse
Great, thanks
Qestion do u just want working magisek root on pettyl ?
There 2 ways
One download magisek manager
Get a twrp buckup of your boot image
Go to magisek manager choose patch boot image and choose your twrp buckup boot image (turn off compression of buckup when taking it ) after it finishes go find the patched boot image it should be in downloads or magisek folder can't remember then go to twrp and flash the patched boot image
/
Second way is to add the fstab or whater its called skip the adb mount part and only do the adb push part (look in tread for exact) https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323 then flash the magisek 18.0 tell me did it work after. here the twrp that should work for every ones pettyl [ https://drive.google.com/file/d/1VsZRGkBujHay02a1M14eJM87H_RHFE9J/view?usp=drivesdk ] !Im not responsible if u brick your phone
!!try to boot twrp before u flash do fastboot boot (twrp image just drag the file to cmd to avoid path erors )
plscotland said:
Qestion do u just want working magisek root on pettyl ?
There 2 ways
One download magisek manager
Get a twrp buckup of your boot image
Go to magisek manager choose patch boot image and choose your twrp buckup boot image (turn off compression of buckup when taking it ) after it finishes go find the patched boot image it should be in downloads or magisek folder can't remember then go to twrp and flash the patched boot image
/
Second way is to add the fstab or whater its called skip the adb mount part and only do the adb push part (look in tread for exact) https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323 then flash the magisek 18.0 tell me did it work after. here the twrp that should work for every ones pettyl [ https://drive.google.com/file/d/1VsZRGkBujHay02a1M14eJM87H_RHFE9J/view?usp=drivesdk ] !Im not responsible if u brick your phone
!!try to boot twrp before u flash do fastboot boot (twrp image just drag the file to cmd to avoid path erors )
Click to expand...
Click to collapse
Yeah, Ive been skipping the mount vendor and pushing Fstab via ADB whilst in twrp.
I'll give this twrp a whirl later this evening when my kids laptop is available
I've bricked my E5 and cannot get past "decryption unsuccessful."
Stock/los15/any other gsi I tried.
Reflashed stick but getting errors flashing gpt.partition.
Everything else then shows errors after each command.
Twrp- i followed your 1st step with a magisk altered boot image.
Tried second step and that failed.
I had to combine both steps into one and twrp then booted and flashed successfully to the recovery partition.
Adb pushed fstab before flashing twrp to recovery but once rebooted to stock I got "decryption unsuccessful" error and got into a bootloop.
Reflashed stock then los15.1 but same again.
Reflashed stock but gpt partition and system sparsechunk.2, 3 and 4 give errors.
Cannot flash stock or gsi currently or reboot to recovery, just keeps going back to fastboot.
bubba1601 said:
I've bricked my E5 and cannot get past "decryption unsuccessful."
Stock/los15/any other gsi I tried.
Reflashed stick but getting errors flashing gpt.partition.
Everything else then shows errors after each command.
Twrp- i followed your 1st step with a magisk altered boot image.
Tried second step and that failed.
I had to combine both steps into one and twrp then booted and flashed successfully to the recovery partition.
Adb pushed fstab before flashing twrp to recovery but once rebooted to stock I got "decryption unsuccessful" error and got into a bootloop.
Reflashed stock then los15.1 but same again.
Reflashed stock but gpt partition and system sparsechunk.2, 3 and 4 give errors.
Cannot flash stock or gsi currently or reboot to recovery, just keeps going back to fastboot.
Click to expand...
Click to collapse
in fastboot enter (use cmd powershell gives erorrs) fastboot -w
And then try rebooting it can take a while and tell me did it fix the problem
Recuperación TWRP 3.3.1-0-Pettyl
Hola buen día soy de Guadalajara México
A mí sí me funcionó está recuperación para rotear con magisk e instalar un mood de píxel.
La instalación de TWRP3.3.1-0-PETTYL Lo hice gracias a la aplicación Root essentials en el apartado flasher flasheando la imagen de la recuperación y ya dentro de la recuperación hice una copia de seguridad e instale magisk
Mi dispositivo es el Moto e5 play go pettyl XT1920-18
Heeeeeelp
(First Sorry for my bad english I'm a Brazilian boy with 17 years old only lmfao)Guys, I have only this little piece of s**** as my phone
#1 and this is not useable, it stop The apps constantely and freezes The system on simple apps (like play music and YouTube)... So I want to leave this cellphone in The trash can and walk away, but I cant make this because i have only this "bombphone"... Anywere can make an downgrade to Android 6.1 or 7.1 to this phone? Seriously I cant live with this phone in this situation. thanks and good night from Brazil
João klebão (supahjohn64) said:
(First Sorry for my bad english I'm a Brazilian boy with 17 years old only lmfao)Guys, I have only this little piece of s**** as my phone
#1 and this is not useable, it stop The apps constantely and freezes The system on simple apps (like play music and YouTube)... So I want to leave this cellphone in The trash can and walk away, but I cant make this because i have only this "bombphone"... Anywere can make an downgrade to Android 6.1 or 7.1 to this phone? Seriously I cant live with this phone in this situation. thanks and good night from Brazil
Click to expand...
Click to collapse
Unfortunately you can't downgrade android versions to 6 or 7, there's no system image / ROM on a lower android version for that device - but what you can do it's flash another GSi (ROM) to give you some usage back.
I also had the the XT1920 pettyl and android go is just awful, so I flashed several different roms to try.
The ones I got to work are
PHHussons lineage 15 (android Oreo)
ASOP 9 (android pie)
Pixel experience (pie)
Out of those lineage was the most stable.
You must remember pettyl only has 1gb ram, and does struggle with android 9 pie - but it does work without too many issues.
You got to learn a whole new process of unlocking the bootloader, flashing a custom recovery, disabling forced encryption and flashing a new ROM.
There are plenty of posts about roms for the E5 play in the threads here, I suggest you take a long read and don't try anything until you feel confident enough to begin because the process to flash roms on pettyl isn't very easy and is quite complex and complicated for a new inexperienced user.
It's quite easy to try that and completely mess up your device so it's unusable.
So, you MUST proceed with extreme caution, don't rush into anything without reading everything ten times, having a coffee and then reading it again another ten times.
Many users have tried to rush this process and then come here crying their phones don't work anymore - this happens because they've tried to rush the process, missed out steps and not read instructions properly........
Not being mean, but it happens all the time.
Edit
If you don't feel confident enough to flash a ROM (and no one will blame you if you don't) unfortunately all you can do is change the way you use your device.
I never noticed any music or you tube video freezing on my pettyl but how I used my device and how you use yours are probably very different.
You can't put lots of apps on android go devices, it doesn't like lots of apps.
You can disable most of the system / Google apps like playstore, Google play music and YouTube and install open source alternatives.
(For instance one plus music, you tube vanced and aurora store to name just three - just Google "disable system apps" or "replace Google apps")
I also tried a couple of launchers, and Librechair go edition or the android Go customised pixel launcher does make quite a significant difference to performance, depending on how much system stuff you disable and how many replacement apps you install.
Edit
I don't have my pettyl any longer so unfortunately that's the only help and advice I can offer you at this time.
Sorry.
bubba1601 said:
Unfortunately you can't downgrade android versions to 6 or 7, there's no system image / ROM on a lower android version for that device - but what you can do it's flash another GSi (ROM) to give you some usage back.
I also had the the XT1920 pettyl and android go is just awful, so I flashed several different roms to try.
The ones I got to work are
PHHussons lineage 15 (android Oreo)
ASOP 9 (android pie)
Pixel experience (pie)
Out of those lineage was the most stable.
You must remember pettyl only has 1gb ram, and does struggle with android 9 pie - but it does work without too many issues.
You got to learn a whole new process of unlocking the bootloader, flashing a custom recovery, disabling forced encryption and flashing a new ROM.
There are plenty of posts about roms for the E5 play in the threads here, I suggest you take a long read and don't try anything until you feel confident enough to begin because the process to flash roms on pettyl isn't very easy and is quite complex and complicated for a new inexperienced user.
It's quite easy to try that and completely mess up your device so it's unusable.
So, you MUST proceed with extreme caution, don't rush into anything without reading everything ten times, having a coffee and then reading it again another ten times.
Many users have tried to rush this process and then come here crying their phones don't work anymore - this happens because they've tried to rush the process, missed out steps and not read instructions properly........
Not being mean, but it happens all the time.
Edit
If you don't feel confident enough to flash a ROM (and no one will blame you if you don't) unfortunately all you can do is change the way you use your device.
I never noticed any music or you tube video freezing on my pettyl but how I used my device and how you use yours are probably very different.
You can't put lots of apps on android go devices, it doesn't like lots of apps.
You can disable most of the system / Google apps like playstore, Google play music and YouTube and install open source alternatives.
(For instance one plus music, you tube vanced and aurora store to name just three - just Google "disable system apps" or "replace Google apps")
I also tried a couple of launchers, and Librechair go edition or the android Go customised pixel launcher does make quite a significant difference to performance, depending on how much system stuff you disable and how many replacement apps you install.
Edit
I don't have my pettyl any longer so unfortunately that's the only help and advice I can offer you at this time.
Sorry.
Click to expand...
Click to collapse
thanks for the tips friend, i flashed some gases from android 9.0 and noticed that 90% of the performance improved which allowed me to played a little free fire lmfao so that unfortunately out of nowhere i faced some crashes and received the message from the user interface you are not responding, right now I am downloading the rom ressurrection remix oreo to see if it will work ... do you happen to know how to build a modified kernel? I have plans to make one for my cell phone but I don't know where to start. obrigado pelas dicas!!!! boa noite do brasil:good:
---------- Post added at 11:14 PM ---------- Previous post was at 11:09 PM ----------
bubba1601 said:
Unfortunately you can't downgrade android versions to 6 or 7, there's no system image / ROM on a lower android version for that device - but what you can do it's flash another GSi (ROM) to give you some usage back.
I also had the the XT1920 pettyl and android go is just awful, so I flashed several different roms to try.
The ones I got to work are
PHHussons lineage 15 (android Oreo)
ASOP 9 (android pie)
Pixel experience (pie)
Out of those lineage was the most stable.
You must remember pettyl only has 1gb ram, and does struggle with android 9 pie - but it does work without too many issues.
You got to learn a whole new process of unlocking the bootloader, flashing a custom recovery, disabling forced encryption and flashing a new ROM.
There are plenty of posts about roms for the E5 play in the threads here, I suggest you take a long read and don't try anything until you feel confident enough to begin because the process to flash roms on pettyl isn't very easy and is quite complex and complicated for a new inexperienced user.
It's quite easy to try that and completely mess up your device so it's unusable.
So, you MUST proceed with extreme caution, don't rush into anything without reading everything ten times, having a coffee and then reading it again another ten times.
Many users have tried to rush this process and then come here crying their phones don't work anymore - this happens because they've tried to rush the process, missed out steps and not read instructions properly........
Not being mean, but it happens all the time.
Edit
If you don't feel confident enough to flash a ROM (and no one will blame you if you don't) unfortunately all you can do is change the way you use your device.
I never noticed any music or you tube video freezing on my pettyl but how I used my device and how you use yours are probably very different.
You can't put lots of apps on android go devices, it doesn't like lots of apps.
You can disable most of the system / Google apps like playstore, Google play music and YouTube and install open source alternatives.
(For instance one plus music, you tube vanced and aurora store to name just three - just Google "disable system apps" or "replace Google apps")
I also tried a couple of launchers, and Librechair go edition or the android Go customised pixel launcher does make quite a significant difference to performance, depending on how much system stuff you disable and how many replacement apps you install.
Edit
I don't have my pettyl any longer so unfortunately that's the only help and advice I can offer you at this time.
Sorry.
Click to expand...
Click to collapse
thanks for the tips friend,
I already work in some way with custom roms since 2013 when I had my lg l1 2 lmfao... i flashed some gases from android 9.0 and noticed that 90% of the performance improved which allowed me to played a little free fire lmfao so that unfortunately out of nowhere i faced some crashes and received the message from the user interface you are not responding, right now I am downloading the rom ressurrection remix oreo to see if it will work ... do you happen to know how to build a modified kernel? I have plans to make one for my cell phone but I don't know where to start. obrigado pelas dicas!!!! boa noite do brasil
So...
The U.S. variants finally have root, this is a very exciting moment for S9/N9/S9+/N9+ users that always wanted to do more with your device. I wanted to create this thread separate from the root thread as I think GSIs are a whole different thing. It's actually pretty simple once you've read, understood and even tried the root method running Oreo Samsung Experience. The steps are very similar but you just swap out the system image.
So please, take the time to read the thread for the Extreme Syndicate root method here: https://forum.xda-developers.com/ga...pment/root-t4041815/post81608559#post81608559
I am going to quote some of the stuff in that thread directly as all of it still applies here.
Please take your time and make sure you follow the instructions carefully.
This method is brought to you entirely by @elliwigy He is the reason for this exploit and method.
With that being said, Extreme Syndicate Root is now available!
Disclaimer:
The Extreme Syndicate team and it's affiliates are not responsible for your actions or your device if any issues are to arise. You flash this and utilize these files at your own risk. You have been warned!
The Adventure!:
I will not get into any technical details here. Just know that this method has taken me ~1 year from start to finish. I also went through a number of devices during this time (at least 7 devices), even sold my original N9 then somehow ended up with another one before this root method was found. Some of us devs might be a bit burnt out so don't get upset if we are not in here all day every day answering everyones questions. We hope users will help eachother, that is what XDA is all about! Also, if you want more real time conversation/support then please join our Telegram group (link posted below) as this is easier for us to moderate and allows discussion to be had in real time. I don't always check XDA messages or PM's as it can be a lot and very tiresome so your best bet is Telegram!
Also, donations/money is not expected or required but if you feel obliged to share what you can then that would be greatly appreciated! Donations keep me on the grind and sometimes can even help me in acquiring other devices to work on. I had issues with Paypal a while back (SamPWND days) and do not have a Paypal account. I do however have a Venmo and Transferwise accounts that work in most situations.
Venmo - http://www.venmo.com/Thomas-Huntington-10
Transferwise - PM @elliwigy for info to donate using Transferwise.
Now Let's get into the files/method!
Click to expand...
Click to collapse
INSTRUCTIONS:
1. Download the following:
- Root files from Extreme Syndicate that belong to your device
- The GSI you want to download (for these devices you need arm64 a-only. With gapps included should be your priority)
- Sh remover zip uploaded here.
- Alternative: ODM nosu zip
2. In odin folder flash the combo firmware
3. Once combo is booted up run the root bat. When done phone will reboot to download.
4. In odin flash the bootswap.tar.md5 file. What this does is swaps the boot and recovery images which allows system to be mounted rw.
5. Now when done flashing you need to hold the buttons to boot to recovery but since we swapped boot and recovery images it will boot system.
6. Now put your phone in airplane mode. This must be done whenever using Flashfire. Copy the system.img (your GSI img) , vendor.img, Sh remover.zip and ODM zip files to your phone.
- NOTE: Flashfire doesn't let you chose the partition on where it's going to flash any image. It decides on where to flash based on the name of the image. So if your gsi is named GSIName-arm64-a-nosu.img then flashfire will have no idea where to flash it. I would rename the img to something like system-GSIName-arm64-a-nosu.img.... or just system.img lol
- NOTE 2: I uploaded a ODM NOROOT.zip. Reason being that some gsi come preloaded with supersu. In theory, using the regular ODM_ROOT.zip from the Extreme Syndicate method should work fine even if the GSI comes prerooted, I just didn't test it with that lol. You should definitely use the root variant if the GSI doesn't say it comes rooted.
7. In Flashfire, choose zip and select the odm zip (root or unrooted, your choice. Read note above). Make sure you select "Mount /system read/write" when the Options pop up. This is necessary or else it will not boot, always chose this on everything. Then choose firmware and choose the system.img and the vendor.img. Then choose data wipe and wipe user and system data (the default choices). Make sure inject super su is NOT enabled. Disable it. Do not let flashfire inject root!!. Then choose zip again and select the Sh remover.zip (select to mount system read/write)
- NOTE: I added the Sh remover zip because some GSI (particularly Android 9 GSI) have a track record of having some problems booting up in Samsung devices. This zip should remove the system/bin/rw_system.sh file. There's no bad side of not having this file on GSI's that don't share this problem, so I'm making it a mandatory step to avoid as much problems as possible
8.. Now click flash. When finished you will have to hold buttons to reboot to recovery until you see boot animation. You must do this on every reboot. If you do not it will reboot to stock recovery. If it reboots to stock recovery just reboot system and hold buttons to reboot to recovery again.
9. When rom is booted up your computer will not recognize the phone for mtp file transfer. Adb does still work so you can transfer stuff that way (you need to switch to ptp transfer method in the dropdown) or use USB adapter and use a thumb drive.
10. Biometrics do not work so don’t try to setup fingerprint or face recognition.
And that's it, you should have your GSI up and running.
Let's keep all the GSI talk on this thread please. I will do my best to keep this thread updated with fixes, compatibility and news. For now, take a look at the confirmed working GSI:
Confirmed working:
- PHH Android 9 GSI
- HavocOS 2.9
- PHH Android 10 GSI (Added bug: WiFi is broken, working on a fix)
Confirmed not working:
- Pixel Experience Android 9
- OxygenOS (Erfan's GSI) (I wouldn't recommend GSI from other OEMs anyway)
ShoutOuts:
@elliwigy For the method and help and everything else
@klabit87 - Ditto
@me2151 - Ditto
@gsm-CHEN - Ditto
@jrkruse - For all the help and support for S9 variants
@everyone else I am forgetting!
ENJOY!
Join is in Telegram where we can discuss GSI and help with problems more quickly
Link: https://t.me/joinchat/HYvgAlUgyqKq9__Y5yg1uA
Reserved 2
Nice guide! I'm sure you'll have plenty of input from others that have tested various gsi.
klabit87 said:
Nice guide! I'm sure you'll have plenty of input from others that have tested various gsi.
Click to expand...
Click to collapse
That's the plan. To hopefully fill this thread with GSIs that work, the ones that don't and any additional fixes to get some to boot.
Great news. Seems HavocOS 2.9 (Android 9) boots pretty well. This is great! Udating post to add link.
EDIT: Also added PHH Android 10. It boots!
just so everyone knows, so far the bugs with the PHH 9 GSI is that no mobile data,messaging and calling will work.
Root on "U" variants! Wahooooo!! Ooo! Ooo!
Anyway, I've been doing this since the galaxy s3 and jailbreaking iPhone since the 3gs... but it's not a every day thing for me and I would assume the same for many others. I do it full tilt "all of my personal time" for a few months get stuff working, backup and then go about my business. I have been forced to switch from my beloved note 4 to this corporate controlled piece or Samsung stuff for $1K and finally someone hacked it! Well done and thank you soooooo very much!!
Anyway, this GSI thing is entirely new to me. I dont know what it is, how it works, what is means etc... it seems to be a relatively new thing. Maybe within the past year or so?
So what I would recomend and ask for is a brief history and explanation of what it is and what is does, where it came from etc... does it make my touchwiz phone like stock android? What aspect of the rom does it replace? System.img I assume but why is it needed? What is the reason it's not needed for Android 8 but is needed for 9 and up?
Of course all of us can google it and and wade through all the documentation on it which I will do and eventually figure it out but I noticed on telegram there are a ton of questions about it since, well, almost everyone has Android 9 on their devices. So it might help in reducing the repetitive questions if there was a quick but detailed write up on GSI from some of you ultra smart type peeps that know about it. My guess is most people won't spend the necessary time required to research GSI which can take days, weeks, months... some of us have kids and demanding jobs and have to cook, clean, repair, work, doctors, school, etc etc.. while others such as myself have opted to go the route of a professional career with no kids and can spend the time researching... Just a suggestion...
Again thank you to all the super smart type fellas and ladies aka DEVs that continue to fight the good fight and make this entire thing possible for the rest of us that are less capable in this area of expertise . You guys rock! Like kick serious @$$ kinda rock!
Zaileion said:
Root on "U" variants! Wahooooo!! Ooo! Ooo!
Anyway, I've been doing this since the galaxy s3 and jailbreaking iPhone since the 3gs... but it's not a every day thing for me and I would assume the same for many others. I do it full tilt "all of my personal time" for a few months get stuff working, backup and then go about my business. I have been forced to switch from my beloved note 4 to this corporate controlled piece or Samsung stuff for $1K and finally someone hacked it! Well done and thank you soooooo very much!!
Anyway, this GSI thing is entirely new to me. I dont know what it is, how it works, what is means etc... it seems to be a relatively new thing. Maybe within the past year or so?
So what I would recomend and ask for is a brief history and explanation of what it is and what is does, where it came from etc... does it make my touchwiz phone like stock android? What aspect of the rom does it replace? System.img I assume but why is it needed? What is the reason it's not needed for Android 8 but is needed for 9 and up?
Of course all of us can google it and and wade through all the documentation on it which I will do and eventually figure it out but I noticed on telegram there are a ton of questions about it since, well, almost everyone has Android 9 on their devices. So it might help in reducing the repetitive questions if there was a quick but detailed write up on GSI from some of you ultra smart type peeps that know about it. My guess is most people won't spend the necessary time required to research GSI which can take days, weeks, months... some of us have kids and demanding jobs and have to cook, clean, repair, work, doctors, school, etc etc.. while others such as myself have opted to go the route of a professional career with no kids and can spend the time researching... Just a suggestion...
Again thank you to all the super smart type fellas and ladies aka DEVs that continue to fight the good fight and make this entire thing possible for the rest of us that are less capable in this area of expertise . You guys rock! Like kick serious @$$ kinda rock!
Click to expand...
Click to collapse
I can sort of give a very brief explanation of sort of how I see it.
And I say sort of because I really don't consider myself an expert, just read a few things here and there
I'm going to go over what "Project Treble" really is, I don't know if you've heard this term thrown around when talking about GSI.
Google made "Project Treble" much more simple with the intention that OEMs would hurry up and release updates faster lol
What happens now is that there is a new partition of where the Android OS takes its resources, and that's the "/vendor" partition. Everything from the drivers to the bluetooth, wifi, sensors, camera, etc.... is found here
Every device that are "Treble" enabled means that they have this "/vendor" partition
So why the S9? Why not the S8, S7, etc...?
Google made it mandatory for all the devices that released with Android Oreo to be "Treble Enabled" out of the box and made it up to the manufacturer to make old devices Treble compatible
But let's not kid ourselves, we all knew that Samsung wouldn't go back on the S8, S7, Note 8, etc... and treblelize them, that's not their style. Though most OEM's didn't do that anyway, there are a very few that actually did.
From the S9 and onwards, all these devices have Project Treble.
So, now we get to what the GSI actually are.
Think of it as ROMs, pretty straight forward.
Now the AndroidOS takes all its hardware resources from "/vendor", these GSI can work on almost all devices out there. Sure there may still exists some compatibility issues here and there but it's much easier to fix them.
So in theory, even if Samsung stops development on the S9 with Android 11, which of course we're all expecting, we can still flash Android 11 GSI when they start coming out because the S9 is Treble enabled
I hope this sort of gave you an idea of what the whole GSI and Project Treble situation is.
PHH Android 9 GSI - Calls no Volume Fix
Just to add onto that, I would like to say that If you are to flash PHH Android 9 GSI and HavocOS 2.9. It doesn't have the calling feature working from the get go. You would be able to make a call to a person, but you won't be able to hear them or they won't be able to hear you. This is an ongoing problem with that GSI. A possible work around for that would be found on
https://forum.xda-developers.com/as...-to/guide-call-fix-patch-gsi-testing-t3791660
Although, I haven't tried it. I am in the process to try and fix this. Will update once done. I cannot thank enough the author and everyone else involved in getting this root to work and along with that being able to flash custom Roms. This is amazing.
What about AOSP 9.0 and 10.0? Do those work?
Mogster2K said:
What about AOSP 9.0 and 10.0? Do those work?
Click to expand...
Click to collapse
I personally haven't tested any more, been busy. You are free to test them yourself and post links to which work. The one consistent bug we did find on Android 10 GSI is broken WiFi.
This works on the 965U, the locked ATT version? This does work on the 965U, I answered my own question.
EDIT: this does not trip knox, sorry for the question. I am RTFM now
Which vendor.img should we use if flashing PHH's GSI 9 or 10?
Mogster2K said:
Which vendor.img should we use if flashing PHH's GSI 9 or 10?
Click to expand...
Click to collapse
The latest Oreo one included in the Syndicate root method
I've run into a problem. I thought PHH's GSI did not have root installed but apparently it does. Unfortunately I flashed ODM_ROOT.zip instead of ODM+NOROOT.zip, and it seems to have broken FlashFire. It's stuck on "Acquiring root access" even tho it already has root. Is there a way to fix this without losing root, or is there another app I can use besides FlashFire? Thanks
Mogster2K said:
I've run into a problem. I thought PHH's GSI did not have root installed but apparently it does. Unfortunately I flashed ODM_ROOT.zip instead of ODM+NOROOT.zip, and it seems to have broken FlashFire. It's stuck on "Acquiring root access" even tho it already has root. Is there a way to fix this without losing root, or is there another app I can use besides FlashFire? Thanks
Click to expand...
Click to collapse
Huh... so now we know that a rooted GSI + the ODM_ROOT zip DOES cause a problem.
Yeah it sucks that on some GSI, the devs don't disclose it's got SU binaries already
What I would do is to look inside one (or both) of your SU apps and see if Flashfire has requested for SU access and it's got it negated for some reason.
If not, then I would just start over with the whole rooting process
Mogster2K said:
I've run into a problem. I thought PHH's GSI did not have root installed but apparently it does. Unfortunately I flashed ODM_ROOT.zip instead of ODM+NOROOT.zip, and it seems to have broken FlashFire. It's stuck on "Acquiring root access" even tho it already has root. Is there a way to fix this without losing root, or is there another app I can use besides FlashFire? Thanks
Click to expand...
Click to collapse
Also clear the data for flashfire and force close it. I. The past we had to just grant all su permissions to get it to work flashfire has been real buggy on s8 and up sometimes
Safe strap possibly.
ShaDisNX255 said:
Huh... so now we know that a rooted GSI + the ODM_ROOT zip DOES cause a problem.
Yeah it sucks that on some GSI, the devs don't disclose it's got SU binaries already
What I would do is to look inside one (or both) of your SU apps and see if Flashfire has requested for SU access and it's got it negated for some reason.
If not, then I would just start over with the whole rooting process
Click to expand...
Click to collapse
Yeah, that's what I ended up doing. I managed to get the rooted Oreo image installed. Another note: PHH 10 v213 does not work with Spectrum Wireless (code CHA). I had no wifi and no mobile data and was stuck on the Google setup for a long time. Anyone here have Spectrum working on a GSI?
Just confirmed that Spectrum Wireless data doesn't work on PHH 9.0 v123 either.