Database Info

Rooted Honor Note 10 : install GSI ROM ?

Hi guys,
Well, title says it almos all...
After reading several posts here, I decided to go for a code to unlock my bootloader and I was successful at that.
I also install TWRP as a custom recovery and I was successful at that too.
I tried then to root the phone, and I could do it.
So I was wondering : as Huawei does not release any source code, would it be possible to install a GSI ROM on that device to get rid of EMUI ?
Anyone tried that ?
Would love to hear an answer, especially if it is "Yes, I did it and it works like a charm"
Regards.

First you need someone with the ability to create said rom.

Hi,
I am taking about a GSI ROM.
GSI stand for "Generic System Image".
It means that it is a ROM that is, in theory, installable on EVERY device that supports Treble project.
And, according to Google policies, for a device released with Oreo as a main system, it is MANDATORY to support Treble...
But of course, manufacturers always do it their way... and can't care less about Google's guidelines.
So the question is : is Honor Note 10 Treble compatible ?
Regards.

Hi,
Well, I am investigating this a little further...
I just checked if the device is (in theory) Treble enabled...
And guess what ?
"adb shell getprop ro.treble.enabled
true"
So, this is encouraging...
I will try to install a GSI ROM on this device. I assume that I will still be able to reflash the other original ROM in case this goes wrong.
At least I hope to be able to do so !!!
Regards.

I managed to install the AOSP project treble but with something that did not work, for example the fingerprint or the 4G network was poor

SmartPhonesFan said:
knew it it will be crap .. this won't work dat won't work ..
Click to expand...
Click to collapse
I do not recommend installing the GSI for the time being
I had also installed a Resurrection Remix without success, blocking the unlock code of the phone and did not make me go on

Samsung Galaxy XCover SM-G398F/FN/DS Adnoird Q boot.img patch, root?

Hi,
What about this device ?
All I could find was "Galaxy XCover 4s SM-G398F/FN Pie 9.0 using Magisk"
All I want to do is install Magisk or LOS but LOS was I think not yet supported (quick search) and old boot.img
device info;
Samsung Galaxy XCover 4s SM-G398F/FN/DS​
One UI 2.0
Android 10
Knox 3.5 API lvl 31 TIMA 4.1.0
Kernel 4.4.177-18237086
Build QP1A.190711.020.G398FNXXS5BTD2
Security software version
- ASKS v3.1 release 20200120
- ADP v3.0 release 20191001
- SMR may-2020 release 1
Android patch level May 1 2020
I haven't updated the rom on the device because this would only makes it harder for me...
Can it run TWRP or any custom recovery unsigned I am willing to experiment with boot.img on my device because without root this phone is useless for me (side load without flashing, like I always do). Have too much phones here for testing but most of them are slow to the snail due to outdated SoC and latest OS/kernel.
let me know I can dump boot.img and we can have fun experiments.
Not sure if this device is able to downgrade rom using odin or if Knox has ARP.
Any hits on next step? Don't feel like wasting lots of time phone is for RE and testing. Nothing special.

How to Patch Stock Boot Image (IMG) using Magisk Manager and root
Once you are sure that you are done with the backup stuff, please proceed to the tutorial below on "How to Patch Stock Boot Image (IMG) using Magisk Manager."
droidfeats.com

As you said there is no lineage os. Just check if your phone supports project treble by downloading treble check app. If supported, you can install variety of andorid 11 roms

Tab E said:
As you said there is no lineage os. Just check if your phone supports project treble by downloading treble check app. If supported, you can install variety of andorid 11 roms
Click to expand...
Click to collapse
Yay just what I needed. System-as-root: supported.
Thanks for that, yeah just got some time to check it out so well, thats neat.

Blu Vivo XL4 Rooting and Custom Rom Questions

I want to root this phone, mainly to turn off dm-verity because it keeps popping up even after a factory reset and this may be my only good option, but what custom rom should I use for this? I tried looking around and couldn't find any recommended ones. Blu Vivo XL4 android version 8.1.0 and the roms I looked at (Corvus OS, AOSPExtended) did not list my device for the downloads at all. Any suggestions or help for rooting this thing? First proper rootable phone I have gotten and I'm not sure the best process for this.

Jewel724 said:
I want to root this phone, mainly to turn off dm-verity because it keeps popping up even after a factory reset and this may be my only good option, but what custom rom should I use for this? I tried looking around and couldn't find any recommended ones. Blu Vivo XL4 android version 8.1.0 and the roms I looked at (Corvus OS, AOSPExtended) did not list my device for the downloads at all. Any suggestions or help for rooting this thing? First proper rootable phone I have gotten and I'm not sure the best process for this.
Click to expand...
Click to collapse
Vivo doesn't allow bootloader to be unlocked

That's nonsense, I can enable OEM unlocking in the developer settings, ain't that what's required?

Austinredstoner said:
Vivo doesn't allow bootloader to be unlocked
Click to expand...
Click to collapse
It's not Vivo company! That's a BLU company.
Jewel724 said:
I want to root this phone, mainly to turn off dm-verity because it keeps popping up even after a factory reset and this may be my only good option, but what custom rom should I use for this? I tried looking around and couldn't find any recommended ones. Blu Vivo XL4 android version 8.1.0 and the roms I looked at (Corvus OS, AOSPExtended) did not list my device for the downloads at all. Any suggestions or help for rooting this thing? First proper rootable phone I have gotten and I'm not sure the best process for this.
Click to expand...
Click to collapse
You need a special steps for work. Not a exclusive file to your phone because GSI (actual custom rom for any device with Android 8.1 and next android version) need some files to fix booting that in your device. But the happy notice is about actual GSI files not need very files for fix or maybe nothing.
Try install AOSP from phhusson Android 9 and Android 10 repository to know. Other great GSI is crDroid by eremitein or other GSI files by him. Need testing.

DragonPitbull said:
It's not Vivo company! That's a BLU company.
You need a special steps for work. Not a exclusive file to your phone because GSI (actual custom rom for any device with Android 8.1 and next android version) need some files to fix booting that in your device. But the happy notice is about actual GSI files not need very files for fix or maybe nothing.
Try install AOSP from phhusson Android 9 and Android 10 repository to know. Other great GSI is crDroid by eremitein or other GSI files by him. Need testing.
Click to expand...
Click to collapse
I'm on.. what's it called, Oreo? Android 8. Not sure if that's going to cause any trouble for roms.

Jewel724 said:
I'm on.. what's it called, Oreo? Android 8. Not sure if that's going to cause any trouble for roms.
Click to expand...
Click to collapse
Yes! Android 8 from very OEMs/companies not have Treble/GSI compatibility.
Only Android 8.1 has that.
Update: Install this app https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=en-US in the phone and know what architecture your phone/firmware has. That will show you which type of GSI file you can test.

Listing what that app says..
Required Image: Needs an image file named system-arm64-aonly.img.xz
Treble and VNDK: Supports legacy version of Treble, using VNDK version 27.0
System as Root: Does not support, use an a-only OS.
ARM-64 archetecture.
Seamless Upgrades not supported.
Does not use Dynamic Partitions.
Unless I missed anything, is this what was needed? Also I am on 8.1.0 for android version, I didn't know if that was just Oreo or if 8.1 had it's own name.

Jewel724 said:
Listing what that app says..
Required Image: Needs an image file named system-arm64-aonly.img.xz
Treble and VNDK: Supports legacy version of Treble, using VNDK version 27.0
System as Root: Does not support, use an a-only OS.
ARM-64 archetecture.
Seamless Upgrades not supported.
Does not use Dynamic Partitions.
Unless I missed anything, is this what was needed? Also I am on 8.1.0 for android version, I didn't know if that was just Oreo or if 8.1 had it's own name.
Click to expand...
Click to collapse
In the first update Android 7.1 [Nougat] to 8.0 and after upgrade to 8.1 [Oreo]. Normal.
All informations good to know what GSI you should test.
Now you can install with fastboot or Custom Recovery [TWRP]. So if has is better and fast.
If not so can using fastboot commands.
Obviusly need bootloader unlocked!
You can read and find more threads but this is good: https://forum.xda-developers.com/t/guide-blu-vivo-xl4-vivo-xi-vivo-xi.3877294/
The only part I should warn you about is the loss of IMEI. So soon as you can do backup from your phone the files NVRAM; NDATA; NVCFG with SPFT or other way like fastboot you won't have wasted time and hassles.

DragonPitbull said:
In the first update Android 7.1 [Nougat] to 8.0 and after upgrade to 8.1 [Oreo]. Normal.
All informations good to know what GSI you should test.
Now you can install with fastboot or Custom Recovery [TWRP]. So if has is better and fast.
If not so can using fastboot commands.
Obviusly need bootloader unlocked!
You can read and find more threads but this is good: https://forum.xda-developers.com/t/guide-blu-vivo-xl4-vivo-xi-vivo-xi.3877294/
The only part I should warn you about is the loss of IMEI. So soon as you can do backup from your phone the files NVRAM; NDATA; NVCFG with SPFT or other way like fastboot you won't have wasted time and hassles.
Click to expand...
Click to collapse
I'll give it a shot. In terms of performing a backup, I would assume that' typical "copy all files on phone to desktop folder just in case"

I should've mentioned, I don't have an SD card in my device, just a SIM card. I don't think I can use TWRP, which is going to complicate matters.

Hello I have a Blu Vivo XL4 android 8.1.0 Oreo, I'm trying to install a custom rom, I looked everywhere not a single rom is made for Blu phones.
bootloader unlocked
according to treble info:
System-arm64-aonly.img.xz
Your device supports the legacy version of project treble using VNDK version 27.0
Use an A-ONLY operating system
ARM64
Seamless upgrades are not supported
NO dynamic partitions
HELP
thanks

Lineage not dialing or receiving calls

I have a Samsung S10e, Exynos, SM-G970F. I have unlocked bootloader, and loaded Lineage OS. I tried both Lineage 18.1 and Lineage with MicroG 18.1. I cannot place or receive calls. I am using Mint Mobile. Someone told me:
Looks like your carrier requires VoLTE which is not supported on any Samsung device running AOSP based ROMs
Is this the case?
This S10e works fine with factory firmware.
I am able to use CalyxOS on a Google Pixel 3 with the same SIM card. It works flawlessly. The S10e is much less expensive than a Pixel 5, and the Pixel 4 has too short of a battery life (unhappy with camera on Pixel 3 compared to S10e).
I am even able to root in Lineage, but not stock firmware (I cannot get the button combination right to start in Magisk root, although I have it installed). I have the August 2021 firmware, so I cannot revert back even one step. I have not found any workaround, even trying the Samsung 80% firmware (would not flash with Odin). I cannot get Flashfire to work, as the root of Magisk 23 is not supported (an earlier Magisk was, but I cannot root with that - I think 20 was the lowest that would, but it always wants to update).
I read that /e is available for my device and supports VoLTE. Is this true? It looks much harder to install - I have to use Heimdall. I used Odin and TWRP for Lineage.

Yeah, I have an SM-G970F as well, running on T-Mobile. I've loaded LineageOS with microG 18.1 on it and I also am having plenty of trouble dealing with VoLTE. I've tried so much different stuff, contacting my carrier, force enabling the VoLTE provisioning, modifying build.props - nothing. I can only receive calls over 3G, and I will get one out of every ten calls when I'm running on LTE. It's also strange to me that you can't place calls, I can do it fine, even when I'm connected to LTE - my phone just disconnects from LTE when I start the call. Does your phone not do that?
I was taking a look at /e/ OS and VoLTE compatibility myself, I couldn't really find anything about it. If you ever install /e/ OS on your S10e, please let me know if there is a VoLTE option - I'll do the same, because I'm considering installing it at this point.
Also, you don't need Heimdall to install /e/ OS. In these instructions they are just using Heimdall to install the /e/ OS Recovery onto the recovery partition, and then installing /e/ OS itself by formatting the phone and sideloading the .zip file. You can just as easily use Odin to flash the recovery partition. If you have TWRP installed you don't even need to bother with the /e/ OS Recovery (unless you really want it). You can just wipe your phone from TWRP and flash the downloaded /e/ OS .zip from there.

I just installed /e/ on my Galaxy S10e (SM-G970F) and I can confirm VoLTE isn't available. I guess it's true that AOSP ROMs on Samsung devices don't support VoLTE.

OnePlus 8T Widevine Issues (L3 or L1 with bad system id)

I have an International KB2005 OnePlus 8T. I had it working great on official Evolution X, F15 firmware copied to both slots, rooted with Magisk Delta 6, passing SafetyNet, banking apps, streaming apps EXCEPT for Netflix. I turned on Netflix spoof in The Evolver settings but this only let it install, when I launched it it would just hang forever.
I checked my Widevine info with DRM info. At the time I had L1 but an invalid System ID (very long digit, way longer than 5 numbers but I don't remember.) I'm pretty sure that was the issue based on some conversations I had.
Ok so I want to fix my widevine giving it L1 with a valid system ID. So I do the "nuclear" option and msmtool back to OOS 11.0.7.9. msmtool completes successfully, bootloader is locked but now widevine is L3 with System ID 8159.
I don't have any original backup files from the phone, I also didn't try the older msmtool to the earlier OOS release. What is the correct way to not only get L1 widevine with a valid system ID on OOS, but what's the correct procedure to unlock bootloader, install a ROM and still retain L1?
TL;DR: how to get L1 widevine with valid system id on KB2005?

I was on the same page as you. I tried searching everywhere and didn't find about it anywhere. There isn't any way to fix the system id as of now. However there is a workaround to get netflix working, if thats what you are trying to do.
Step 1: MSMtool back to oos 11.0
Step 2: Unlock bootloader. (it changes the system id to 4 digit number which is L1 secrity)
Step 3: Install netflix and other apps that dont work with broken system ID. Log in your account.
Step 4: Update your rom.
System ID breaks but your apps works fine.

AstronxD said:
I was on the same page as you. I tried searching everywhere and didn't find about it anywhere. There isn't any way to fix the system id as of now. However there is a workaround to get netflix working, if thats what you are trying to do.
Step 1: MSMtool back to oos 11.0
Step 2: Unlock bootloader. (it changes the system id to 4 digit number which is L1 secrity)
Step 3: Install netflix and other apps that dont work with broken system ID. Log in your account.
Step 4: Update your rom.
System ID breaks but your apps works fine.
Click to expand...
Click to collapse
So when going from OOS 11.0 to a custom ROM, are you suggesting to dirty flash and not wipe data (I always thought this was a terrible idea)? Or still do a clean flash of the ROM then re-install those apps and it will work?

It is a terrible for some ROM
Dopamin3 said:
So when going from OOS 11.0 to a custom ROM, are you suggesting to dirty flash and not wipe data (I always thought this was a terrible idea)? Or still do a clean flash of the ROM then re-install those apps and it will work?
Click to expand...
Click to collapse
I had tried restoring with titanium backup but the results were same, they dont work. So yeah dirty flash is a terrible idea for some rom while some ROM allow dirty flashing. I have only tested on updating ROM from OOS 11 to OOS 13 and its working.

AstronxD said:
It is a terrible for some ROM
I had tried restoring with titanium backup but the results were same, they dont work. So yeah dirty flash is a terrible idea for some rom while some ROM allow dirty flashing. I have only tested on updating ROM from OOS 11 to OOS 13 and its working.
Click to expand...
Click to collapse
I've never ever ever seen a ROM that doesn't require a wipe when going from stock to the ROM. However once you're on the ROM, you can usually dirty flash updates unless the maintainer specifically says a new build requires a clean flash. Maybe this would work if there was a modified ROM based on OOS.
I appreciate your responses, but OOS 13 is the worst version of Android I've ever tried. I guess my dream of getting the 8T working with an A13 AOSP/LOS based ROM is still dead (with the valid L1 cert, otherwise it works fine).
I'm sticking with Pixels from now on. On every Pixel I've ever messed with (3a XL, 5a 5G RIP mobo, 6a, 7 Pro) I've been able to do anything- unlock the bootloader, try any custom ROM and/or kernel, use a custom recovery, have safetynet passing or failing and the valid L1 widevine cert just persists. Seems like a silly reason to dump OnePlus, but I need that valid L1 cert and I'm not willing to stay on the good, outdated OOS 11 or use the terrible, new OOS 13.