Related
Finally got my phone yesterday and I had some questions. Perhaps some existing users with the phone can answer them.
For the sake of this post, keep the following in mind about the status of my phone:
bootloader - unlocked
custom recovery installed - twrp 3.0.3-1
1. My phone came, it had OOS 3.5.4 installed on it. After I unlocked the bootloader and put twrp on there, I couldn't help trying to get OOS 4.0.2 on there. I followed the 3rd post here to update to 4.0.2: https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Regardless of whether or not I try to flash su or magisk, I get the dm-verity message upon booting to system. I just hit the power button to skip the message, but is this normal with flashing the nougat oos? These roms are tock, so I would assume nothing would trigger it unless it's being triggered by twrp? I tried flashing the dm-verity-encryption-fix 5.1 and this doesn't seem to do anything either.
NOTE: I don't get any dm-verity message UNTIL after I flash the stock OOS 4.0.*
with 3.5.4 there were no problems even with custom recovery and magisk installed.
2. I feel really stupid, but I have been wanting to format the system to F2FS partition. In twrp I goto wip --> advanced wipe --> check "system" --> change partition --> check F2FS --> and continue... It says System has been formwatted, if I reboot it tells me there is no OS, so I go back into twrp and reflash the full stock 4.0.2 rom, but then each time my partition goes back to Ext4. Am I missing something??
3. In OOS, is there a way to create folders in the app drawer? I would like to organize my apps.
4. Has anyone figured out a way to get Xposed to work on 4.0.2?
Overall experience with my new phone; I absolutely LOVE it!!!! The phone is fast as hell and responsive as all getout. I honestly think this is the best phone I have ever owned. The fingerprint scanner is insanely quick at unlocking the phone. Initially I was concerned about the physical size of the phone, but it's actually not bad. It's large, but still easy-ish to hold and use. The back camera seems to be VERY sensitive to movement, so I see what people mean when they say images come out a little blurry. The front facing camera is actually really good though IMO. It seems to take pics fine and focus much better on the image.
My wifi signal isn't bad. I don't seem to have any issues with this, and the battery is phenomenal too. I installed forcedoze and leandroid and this phone just isn't phazed by anything. I look forward to using it more today to put it to the test.
1. That's normal. Everyone with TWRP and OOS4.0+ has that message at boot.
2. I am not qualified to answer this question. Sorry.
3. No, but you can download a custom launcher that may be able to do that. I'm 99.98% sure that there is a custom launcher on the Play Store that can do that.
4. Nope. Xposed has not yet been developed for Android Nougat.
Awesome, thanks for your reply! I was concerned at first I was doing something wrong with the install since I kept getting that dm-verity warning.
2. You cannot and really shouldn't format system to f2fs without custom kernel support.. even then.. why would you do it?
Data is already f2fs and it is enough.
V 2.0 said:
2. You cannot and really shouldn't format system to f2fs without custom kernel support.. even then.. why would you do it?
Data is already f2fs and it is enough.
Click to expand...
Click to collapse
Well from what I read F2FS would be the better option since it's optimized for UFS. I know Data is already F2FS, but I figured if system was formatted as f2fs as well, it would launch stuff quicker (even though it's already super fast imo)
Just don't. As I said, won't work on stock for sure and there are no custom kernels yet. Even then I say don't.
Thanks for the feedback! I appreciate it! I'll leave the filesystem the way it is.
Do any of you use custom launchers? From what I'm seeing Apus Launcher and Nova Launcher are the recommended ones, but I'm leaning towards Nova Launcher to better organize my app drawer. Any suggestions?
I am happy with stock launcher, but if you wanna organize app drawer better I also heard only the best about Nova.
Hi someone with an account on 4dpa with 30 posts could please download this rom and share it here? I don't know Russian so it's impossible for me to write 30 posts.
I have a Zenfone Go (Z00VD) and the stock ROM it's terrible (crash in the camera, 1 Gigabyte of app space already full....)
In case you can't, could you provide an alternative ROM with as less bugs as possible?
Thank you
Original Thread 4pda
Translated Google
Guess we're on the same boat buddy. Have you tried the other ROMs on their forum like the nougat ones? They seem nice.
I personally prefer to use the RR 5.5.9 lollipop rom provided by 4pda since for some reason the nougat and marshmallow roms on their site just give me bootloops. It may be different for you though.
JustAnormalGuy said:
Guess we're on the same boat buddy. Have you tried the other ROMs on their forum like the nougat ones? They seem nice.
I personally prefer to use the RR 5.5.9 lollipop rom provided by 4pda since for some reason the nougat and marshmallow roms on their site just give me bootloops. It may be different for you though.
Click to expand...
Click to collapse
Hi, not yet, it's not my phone so I'm searching a stable ROM. I saw the nougat thread here but it's not very clear what works and what not, there seems to be a nougat rom on 4dpa which should work well except the videocamera with the stock app, but the Oreo one seems almost bug free although more complex to install. Unfortunately I can't access it.
Hello,
From what I can tell, both Oreo and Nougat ROMs were unstable and/or sluggish for me, so I'd recommend to stick to Marshmallow based ROMs(for now). My personal preference is ResRemix 5.7.4, but if you decide to try any of them, keep in mind that ROMs with kernel 3.18.19(as far as I've seen most of ROMs in that thread) all have these two issues that I was able to find so far:
Notification LED doesn't work
Bluetooth audio doesn't work either
Other than that, the ROM is super-stable and somehow better than 5.1.1 ROMs from official dev thread there.
And for JustAnormalGuy, bootloops in later ROMs seem to happen because of unwiped internal storage(basicly needs entire /data partition wiped somewhy). Try marking the 'Internal SD' option when wiping partitions for ROM installing.
Good luck!
aurismat said:
Hello,
From what I can tell, both Oreo and Nougat ROMs were unstable and/or sluggish for me, so I'd recommend to stick to Marshmallow based ROMs(for now). My personal preference is ResRemix 5.7.4, but if you decide to try any of them, keep in mind that ROMs with kernel 3.18.19(as far as I've seen most of ROMs in that thread) all have these two issues that I was able to find so far:
Notification LED doesn't work
Bluetooth audio doesn't work either
Other than that, the ROM is super-stable and somehow better than 5.1.1 ROMs from official dev thread there.
And for JustAnormalGuy, bootloops in later ROMs seem to happen because of unwiped internal storage(basicly needs entire /data partition wiped somewhy). Try marking the 'Internal SD' option when wiping partitions for ROM installing.
Good luck!
Click to expand...
Click to collapse
Those 2 bugs are not a deal breaker for me, would you mind linking to the ResRemix 5.7.4 rom that you used?
Sure, buut since I can't post links(thanks XDA for 10 post restriction, love ya!), I'll have to send one another way.
PM me your Discord handle(if you have one) or something else. I should be able to send you the link there.
aurismat, and what version of twrp do you use ?
I use TWRP 3.0 by Jemmini. It's been a *long* time since I installed it though, so if you have something different, I'm afraid I won't be of much help unless I'll be able to pull my recovery .img file.
Actually, i use the same version. Problem is most probably my method of root. The common method of rooting for our device didn't include any flashing with sp flash tool. But for my situation, my bootloader is locked even after downgrading. So i did the other method (also found on the forum) in which includes flashing.
Hmm, it *may* be the root method, may be also the locked bootloader.
If I recall right(and this might be THE common way), I used the fastboot method from XDA, and I knew it'd work cause I rooted more phones that way. I remember downgrading the stock ROM down to version 39(i think that one still had the bootloader check in dev options) and then trying to unlock the bootloader and obviously go through flashing the recovery image.
Dunno what might be the issue with your way of flashing, though. AFAIK might be anything from leftover files to bootloader giving the finger.
@aurismat i think the problem might be that i used the "format all + download" option on sp flash tool. Does that affect the phone in any way that deprives my phone from using 6.0 - 7.0 roms? (Besides the "null" imei effect)
@JustAnormalGuy I don't think it should be a problem, because the ROM .zips install their own stuff to the partitions AFAIK, so even if Flashtool wipes everything, it should still be fine. Try doing one of them ROMs(previously said ResRemix worked for me), but remember to wipe the Internal Storage partition if you can.
Oh and remember to take a backup of your current ROM, should it bootloop again at least you won't have to do the hassle of reinstalling everything back(learned that the hard eay haha).
EDIT: was it just Nougat ROMs that you were trying or was it both Nougat and Marshmallow? Not sure what might be the cause, but the ROMs developed under the same kernel from ska-vova in 4PDA worked for me. Just a thought.
well actually i already tried various roms from Marshmallow to Nougat all of which gave me bootloops. I've already followed the steps of installation as written. However, i tried once installing a Marshmallow rom from the facebook group named "ASUS Zenfone Go Indonesia" and it surpisingly worked for me (numerous bugs present however), as well as most of the marshmallow (and only marshamallow roms) on their group.
The thing is I also might think one of the reasons why i get the bootloops in the roms from the 4pda forum is the kernel used in them. (just speculation) Should it be correct to assume that ?
As I recall:
Working rom shows "kernel version > [email protected]"
Not working rom - "kernel version > [email protected]"
Hmm, I'm using [email protected] kernel version 3.18.19.
All the ROMs there seem to be by mosly nik-kst's kernel. ska-vova seems to just build ROMs with the kernel.
Besides, take note from the working ROM - it's also from 4PDA.
Only thing I can speculate is that your device is somewhat different(maybe different hardware, not sure) and hence why it gives you BLs.
Dunno, this case is a tough cookie to be honest - only thing I can recommend at this point is to flash literally EVERYTHING back to stock and try using fastboot method to get recovery and root back.
Hey @Darkorn,
Over the span of a few days, I've tried installing 4PDA's Oreo ROM.
It took me a good couple of headaches to make out what translated Russian meant in the instructions, but I've managed to repartition the entire device to the guide.
Seems to work properly so far, hell even Bluetooth and Notification LED issues from older ROMs seem to be fixed!
Though one thing that annoys me *personally* is that it's impossible to install SuperSU, so you're stuck with Magisk. It's not the end of the world, though, as long as you don't care about SafetyNet's BS.
Oh and @JustAnormalGuy, try repartitioning your device according to the Oreo instructions in 4PDA, that might be the solution for ya.
If I ever get up to 10 posts I'll ask those guys permission to let me post the tutorial here with all the links(hopefully).
Until then, good luck to both of ya!
aurismat said:
Hey @Darkorn,
Over the span of a few days, I've tried installing 4PDA's Oreo ROM.
It took me a good couple of headaches to make out what translated Russian meant in the instructions, but I've managed to repartition the entire device to the guide.
Seems to work properly so far, hell even Bluetooth and Notification LED issues from older ROMs seem to be fixed!
Though one thing that annoys me *personally* is that it's impossible to install SuperSU, so you're stuck with Magisk. It's not the end of the world, though, as long as you don't care about SafetyNet's BS.
Oh and @JustAnormalGuy, try repartitioning your device according to the Oreo instructions in 4PDA, that might be the solution for ya.
If I ever get up to 10 posts I'll ask those guys permission to let me post the tutorial here with all the links(hopefully).
Until then, good luck to both of ya!
Click to expand...
Click to collapse
Nice! Resurrection Remix is working too well to bother, but who knows in a few months!
That would be great man, thanks !!
So it seems TWRP might be an issue getting it on our Pixel 4's.
According to @Dees_Troy, its a problem. Seems they don't even have one for the Pixel 3 on Android 10.
@Dees_Troy
"Pixel 4 is in real danger of not getting TWRP for a while after it's released due to all of the changes made in how recovery works in Android 10."
https://mobile.twitter.com/Dees_Troy/status/1171151359564890113
We'll see, fortunately we know we have a working magisk and that actually takes care of everything I do although I miss the convenience of TWRP, no question. The guy seems to work miracles so I wouldn't be surprised to see him figure it out. If not, I suppose I can only be thankful for everything he's done for us already and wish him luck in his next endeavor. I gotta be honest here, way back on windows phone I was surprised the door wasn't being closed on all this stuff. When Android came along it was like the wild west and I thought there was no way it could go on. Now we're here and iin many respects still having our way with our phone. It's been a pretty good ride.
krabman said:
We'll see, fortunately we know we have a working magisk and that actually takes care of everything I do although I miss the convenience of TWRP, no question. The guy seems to work miracles so I wouldn't be surprised to see him figure it out. If not, I suppose I can only be thankful for everything he's done for us already and wish him luck in his next endeavor. I gotta be honest here, way back on windows phone I was surprised the door wasn't being closed on all this stuff. When Android came along it was like the wild west and I thought there was no way it could go on. Now we're here and iin many respects still having our way with our phone. It's been a pretty good ride.
Click to expand...
Click to collapse
Yea, hopefully I pray he'll figure it out for sure.
Sent from my VS996 using Tapatalk
MicroMod777 said:
So it seems TWRP might be an issue getting it on our Pixel 4's.
According to @Dees_Troy, its a problem. Seems they don't even have one for the Pixel 3 on Android 10.
@Dees_Troy
"Pixel 4 is in real danger of not getting TWRP for a while after it's released due to all of the changes made in how recovery works in Android 10."
https://mobile.twitter.com/Dees_Troy/status/1171151359564890113
Click to expand...
Click to collapse
He will get it there is always a way
Damm that's not good.
Personally, I don't need recovery. My first pixel device and the last thing I want to do is flash some half baked custom ROM for it. Everything I need can be flashed through magisk or EXKM. As long as I can root, I'm good
I'll leave @Dees_Troy's full statement - dated 23rd October 2019 - given on the official TWRP website here as well:
Please note that this post is primary related to TWRP and the Pixel 3 and 4 and devices that may ship in the future that ship with Android 10 as their original version of Android. Older non-Pixel devices that shipped with older versions of Android and receive upgrades to Android 10 are not affected.
Long story short, TWRP support for Android 10 is going to take a while.
Android 10 brings about the largest changes to the way AOSP implements recovery since Google shifted recovery from C to C++ when they moved from Android 4.0 to 4.1 more than 7 years ago. A lot of components in AOSP recovery were moved into subfolders, which makes merging the latest changes into TWRP more time consuming. At least on the Pixel 3, the ramdisk that we use for recovery is now handling part of normal boot in addition to recovery, so we're not sure what the best way will be to go about replacing recovery without affecting the ability to boot up normally. In addition, the way Google is building the ramdisk on the Pixel 3 is a lot different than the past. In the past, the executable binaries in the ramdisk were built as static binaries with no linked libraries. TWRP has almost always been built with separate linked libraries. The new dynamically linked stock ramdisk will make it harder for us to slip TWRP into the ramdisk.
Once we get TWRP compiling with the new changes from 10, we have some additional items that need consideration. As mentioned above, the stock ramdisk is using dynamic linking. Unlike TWRP, the stock ramdisk places the executables and libraries in the usual locations inside a /system folder. Normally TWRP leaves /system alone so that we can mount the system partition to its usual location of /system. If we leave things the way they are on the Pixel 3, mounting the system partition gets tricky. A lot of custom zips depend on mounting the system partition to /system.
Android 10 also introduces a new dynamic partitioning system. Instead of having a dedicated system partition and a dedicated vendor partition, etc. Android 10 uses a super partition. I like to think of the super partition as a partition that contains a bunch of smaller partitions. One of the side effects of this dynamic partition system is that Google has chosen to use a form of the ext4 file system that is for all intents and purposes, read-only. This choice means that even if you wanted to, you can't easily mount and modify the system partition. We haven't really discussed this with other developers yet, but it may impact your ability to do things like install Gapps. In addition, the dynamic partition model means that eventually, we should probably provide you, the user, some GUI driven tools in TWRP to allow you to manage the dynamic partitions that are on the super partition.
On top of all of the above, I, Dees_Troy, am the one who usually handles merges of new versions of Android. My wife is currently pregnant with our fourth child. I am quite busy with my growing family and the need to find a bigger house, so my time for working on TWRP right now is somewhat limited. So, I guess please be patient, or feel free to download the TWRP source code and make the needed changes yourself.
Click to expand...
Click to collapse
Source: twrp.me
My guess is: we got to get familiar with manually patching boot images regarding Magisk, and maybe with flashin ROMs shipping as a GSI (Generic System Image). First time I made such an assumption was, when the first GSIs startet popping up in the respective section here on XDA, and I still guess that this is the way to go for future modding.
5m4r7ph0n36uru said:
I'll leave @Dees_Troy's full statement - dated 23rd October 2019 - given on the official TWRP website here as well:
Source: twrp.me
My guess is: we got to get familiar with manually patching boot images regarding Magisk, and maybe with flashin ROMs shipping as a GSI (Generic System Image). First time I made such an assumption was, when the first GSIs startet popping up in the respective section here on XDA, and I still guess that this is the way to go for future modding.
Click to expand...
Click to collapse
This has been known since before we even got our devices in hand, statement has been shared long ago... When it was new.
wrongway213 said:
This has been known since before we even got our devices in hand, statement has been shared long ago... When it was new.
Click to expand...
Click to collapse
Yes, I know. But I saw yet another thread about TWRP for Pixel on Android 10 popping up, which implies that this thread, as well as this information still isn't widely spread/known as of yet. Just wanted to prevent further TWRP threads popping up on Pixel 4 forums.
Sent from my Google Pixel 4 XL using XDA Labs
5m4r7ph0n36uru said:
Yes, I know. But I saw yet another thread about TWRP for Pixel on Android 10 popping up, which implies that this thread, as well as this information still isn't widely spread/known as of yet. Just wanted to prevent further TWRP threads popping up on Pixel 4 forums.
Click to expand...
Click to collapse
You can't prevent the inevitable. There's always going to some users who don't understand how to use Google or XDA search
GOOGLE Pixel 4XL (coral) - QQ1B.200105.004 - Android 10 . My same rig.
Any updates on TWRP?
kb5rir said:
GOOGLE Pixel 4XL (coral) - QQ1B.200105.004 - Android 10 . My same rig.
Any updates on TWRP?
Click to expand...
Click to collapse
No
Can you boot (not flash) to TWRP on the Pixel 4 XL? The only convenience I'll miss compared to my Pixel 2XL is being able to boot to TWRP and flash Magisk if so...
WorldOfJohnboy said:
Can you boot (not flash) to TWRP on the Pixel 4 XL? The only convenience I'll miss compared to my Pixel 2XL is being able to boot to TWRP and flash Magisk if so...
Click to expand...
Click to collapse
No, it's got to do with the dynamic partitions and mounting /system. From what I've read, even if you booted twrp it would no be functional.
I can only imagine the effects of this dynamic partition on other useful projects like microG...we have our work cut out for us here. I smell innovation!
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.
Hello everyone, try to install several custom roms, there is no tutorial that explains how the rom and twrp are installed. There are many tutorials and they all contradict, some say do this, others say do the other, but all fail.
Twrp boot, flash rom, install custom rom on SLOT A, install TWRP on slot B.
PROVEN ROMS:
PixelExperience:
Very low call volume, impossible to fix.
LineageOS:
Does not start play store, does not allow login to accounts, does not allow to install gapps.
- CURRENT ROM--
Evolution X:
Does not start play store, does not allow login to accounts.
I have been installing customs roms for years and this device is costing me my life. HELP
The most users get in trouble with A/B devices because they don't know exactly the differences between A-only and A/B partitions.
You don't know how to install TWRP? Why? On twrp.me you can find a detailed instruction for every single model.
A custom ROM is always a .zip file and you can flash a .zip file via TWRP. If you flash a ROM while slot _a is set as active you will install the ROM on slot _b. That's all. That is the meaning of semless updates.
Every new ROM must contain a own boot.img. A new boot.img will delete TWRP and Magisk. TWRP is a recovery and A/B devices don't have own partition for recovery. The recovery is merged in the boot partition.
Also Magisk uses the boot.img to patch the ramdisk. Flashing a new boot.img means you override the patched ramdisk with a new own. As a result you need a new Magisk installation.
my recommendation is starting from scratch with a clean stock 10 install then trying again...
lineage wiki probably has the best install instructions https://wiki.lineageos.org/devices/lake/install but also check its forum thread https://forum.xda-developers.com/g7-plus/development/rom-lineageos-17-1-t4076569 for other recommendations . if you want evolution X read the instructions in its thread https://forum.xda-developers.com/g7-plus/development/rom-evolution-x-4-1-69-moto-g7-plus-t4081731 as well but there pretty much the same.... you've probably went threw those threads already based upon you saying you have tried 3 diff roms already, but try again from a clean install of stock 10 (IF you want to run a 10 rom). i know it's not really a "clean/easy/simple" solution/tutorial, but with this device there is some trial and error for getting a half assed working install. however MAKE SURE you are on a stock 10 rom when installing a 10 rom, pixel experience is a 9 rom and that could be part of your problem. moving from android 10 stock, to a 9 rom, then back to a 10 rom will lead to issues. or a 9 rom, to a 10 rom, without moving to stock 10 in between will lead to problems.
as this isnt nearly a widely adopted device, custom rom development and support isnt even close to other devices, so expect bugs. i've always ran cfw's on all my devices ever since the htc g1/dream days, this is my first device i've stuck with stock due to the lack of rom development, lack of widespread use and people actually wanting to use cfw and users to bug report, and stock being more stable... but your mileage may vary. also no disrespect meant towards the hard working dev's who do work on this device, keep it up.
Thank you very much, I feel lucky that you have responded so quickly, sometimes my messages I post in this forum are never answered. Right now I am with revolution X:
--- It has TWRP perfectly installed, it has the boot.img patched with Magisk without any error and rooted perfectly, but google play for more than clean and reinstall it never opens, it does not allow me to login to the accounts, the APPs they close alone, etc.
I will try to put the stock and again but I have very little hope. thanks, again¡¡
prodigy90 said:
Thank you very much, I feel lucky that you have responded so quickly, sometimes my messages I post in this forum are never answered. Right now I am with revolution X:
--- It has TWRP perfectly installed, it has the boot.img patched with Magisk without any error and rooted perfectly, but google play for more than clean and reinstall it never opens, it does not allow me to login to the accounts, the APPs they close alone, etc.
I will try to put the stock and again but I have very little hope. thanks, again¡¡
Click to expand...
Click to collapse
yeah it seems to be pretty finicky getting a good install and gapps seem to have issues. reading all the posts in the lineage17 thread just make me cringe. as much as i'd love to use lineage as my daily driver (or evo X) my days of willing to put up with a buggy rom and daily dirty flashing have come and gone. this was my first, and will be my last, moto device for the the simple fact it just doesnt have the user base and its development is stunted, compared to more widely used devices.
i hope you get something working, the lineage17 thread definetly has some good advice on what people have done to get a working install, should be able to apply flash order etc to a evoX install (minus having to install gapps for evoX)
solved
I managed to perfectly install the Stock Rom with the following tool:
Lenovo MOTO Smart Assistant, a real wonder, simply select the model and in fastboot, immediately install the factory rom.
download.lenovo.com/consumer/mobiles/lmsa_v4.5.0.14_setup.exe
prodigy90 said:
I managed to perfectly install the Stock Rom with the following tool:
Lenovo MOTO Smart Assistant, a real wonder, simply select the model and in fastboot, immediately install the factory rom.
download.lenovo.com/consumer/mobiles/lmsa_v4.5.0.14_setup.exe
Click to expand...
Click to collapse
yup, the LMSA is a great tool for sure. glad you got back to a clean stock install.