Related
Introduction
This is aimed to be a complete but simple guide for users which want to know what works in the Treble-World on the Mate 10 Pro and 'how to get there', based on other guides and my own findings
Disclaimer: I am not responsible for what you do with your device, you are free, probably old enough to know what you are doing and intelligent enough to read this through.
For the moment I will only speak about my own tests on a BLA L29 as I don't have the possibility to test everything.
Feel free to share your own discoveries via PM (just reuse the same formatting to make things easy)
Requirement
1. PC/Laptop running Windows 10 with adb and fastboot drivers installed
2. Original Huawei USB Type-C Cable
3. Being able to read and use search when a question arises
Summary
0. General Information
I. Unlock the Bootloader
II. Choose your ROM (a.k.a "What works on what")
III. Install your ROM
IV. Miscellaneous / Secondary stuff
V. Bonus : What to do if I am stuck / Bootlooping
0. General Information
To make things easier for everybody, here are some basic informations about your device and some common knowledge :
How do I get in Download / Bootloader / Fastboot Mode ?
Shut down your device, insert your USB cable. Keep the Volume DOWN button pressed and press the Power button, wait.
PRO TIPP : You may also get there from within android, first enable ADB debugging in developer options, then, on your PC open a command prompt and type "adb reboot-bootloader"
How do I get in Recovery Mode ?
While in Download / Bootloader / Fastboot Mode, take the USB cable out, keep the Volume UP button pressed and press the Power button until the phone reboots.
I. Unlock the Bootloader
We allready have a thread by @otonieru perfectly discussing this point, don't forget the Windows 10 fix :
https://forum.xda-developers.com/mate-10/how-to/how-to-huawei-mate-10-pro-standard-t3709535
II. Choose your ROM (a.k.a "What works on what")
This section isn't complete and should be detailed with time. None of these ROMs is specific for the Mate 10 Pro, but thanks to Treble, most images will work. Device-specific modifications are still needed in future, ask your local dev
1. Generic AOSP (Android 8.0 and 8.1) by Phhusson
Link : https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
Description : Really basic ROM (basically pure AOSP) which serves as a basis for most of the other ROMs.
What's working : Everything basic
What's not working : VoLTE, SuperSU and Magisk, Signal strength is reported incorrectly, error message at each start, Play Store tends to hang (solution : wipe the Play Store from recents or force close it)
Actual status : Barebones, can be customized in some ways with overlays.
2. LineageOS 15.1 (Android 8.1) by LuK1337
Link : https://forum.xda-developers.com/honor-view-10/development/rom-lineageos-15-1-t3753000
Description : If you don't know LineageOS, you should have heard about CyanogenMod (CM). This is a super clean, customizable version of Android, based on AOSP
What's working : Everything basic
What's not working : VoLTE, SuperSU and Magisk (system crashes), Signal strength is reported incorrectly,
root works thanks to addon-su (see Miscellaneous)
Actual status : Working as a daily driver (at least in my case) if you can live with some very small drawbacks.
III. Install your ROM
Once you have unlocked your Bootloader and chosen the ROM your heart desires follow these steps :
1. BACK UP YOUR DATA ! -> You will certainly have to do a factory reset and backing up data should be something natural when flashing something on your phone, even before updates.
2. Download the ROM (latest is probably best, but it's best to read what is said in the respective threads before jumping in the hole.
3. Reboot to the Download / Bootloader / Fastboot Mode (see above)
4. Flash the ROM by opening a command prompt and typing :
Code:
fastboot flash system system.img
where "system.img" is the filename of the ROM you downloaded
5. Reboot the phone by typing :
Code:
fastboot reboot
6. The phone will probably get in a bootloop. Don't panic. This should be normal.
After 4-5 reboot the phone will go in Recovery mode. Make a Factory Reset
7. Reboot
8. Profit
IV. Miscellaneous / Device-Specific stuff
This is probably the more interesting part as it is quite hard to find the correct information for our device concerning these points.
Root
ROMs as Lineage don't come prerooted. To root your phone the only viable solution seems to be addon-su for the moment.
To install you will need to install TWRP (follow the instructions in this link by @Dees_Troy : https://forum.xda-developers.com/mate-10/development/recovery-twrp-3-2-1-0-touch-recovery-t3752399 ), boot to TWRP (same as booting to Recovery, as TWRP is the new Recovery). go to advanced -> adb sideload. Connect your phone to your PC and flash the file using
Code:
adb sideload addonsu-15.1-arm64.zip
finally reboot, go to 'developer options' and chose the desired option under 'root options'. Done.
Camera
When flashing a ROM it will probably come with the stock AOSP or Lineage camera which, just say it, sucks on our device form a quality point of view. Here are the answers found to this problem for the moment. Sadly, there isn't one solution which works for everything and everyone.
Google Camera - GCam
Photos work - Gallery works - Videos don't work
Right now his is probably the best compromise if you want something that works, easy to install, while not wanting every little gimmick (in that case you should probably stay on EMUI - The definition of gimmick). Simply install the apk.
Note : there are probably other versions of GCam that work or will work in future, feel free to inform me / us about better working versions.
Link : https://drive.google.com/file/d/1Rw2lXtSHvOUalpA8YKg_kW2Xj_Gu746M/view
More information / discussion :
https://forum.xda-developers.com/mate-10/help/gcam-mod-mate-10-t3729078
Camera Port from the Mate 9 - needs root
Photos work - Videos don't work - Gallery doesn't work - Most filters and gimmicks work
A bit more complicated to install. The easiest way found for now is to root first using addon-su and then copy the system folder inside this zip into the respective folders using a root enables explorer like solid explorer
Link : https://mega.nz/#!7hQDhQAK!p2s7jQp9-nhp2-O1U2s2GrBB9UVBhgKDtFfHTq_CHvI
More information / discussion : https://forum.xda-developers.com/pr...huawei-stock-camera-app-treble-roms-t3735169/
V. Bonus : What to do if I am stuck / Bootlooping
Remember when I said to back up ? Well I hope you did, because if you are really bootlooped and a reflash of the system image hasn't helped. you will have to reflash the whole device, which isn't quick.
Gladly @mankindtv has got you covered with his great guide : https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I hope I could help a bit. Feel free to add your own findings, simply PM me.
Credits -
@otonieru for the great Bootloader unlocking thread
@phhusson for his many efforts to make Treble awesome
@LuK1337 for his many efforts to get things working on the Lineage side as well as for addon-su
@Dees_Troy for his awesome work on TWRP
@mankindtw for his great guide on recovering from the loops of boots
reserved
It's gonna be one of the most helpful threads for the novices.
---------- Post added at 02:41 AM ---------- Previous post was at 02:39 AM ----------
If possible, please add how to go back to stock rom in simplified form.
mdjishadk said:
It's gonna be one of the most helpful threads for the novices.
Click to expand...
Click to collapse
I have lost three days to get out of bootloops and gather the info... I hope nobody else will have to live the same thing (and maybe this can become a dedicated thread to fix the last missing blocks to have a complete experience)
good job
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
good job on this one OP btw, video on mate 9 camera port is only broken on 8.1, on 8.0 all camera features work fine except opening of the picture from the camera app itself
Good job man!
Gryphie said:
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
Click to expand...
Click to collapse
It might be android 8.1. It worked fine for me when using 20180225 version, didn't test later ones.
What version are you on?
Gryphie said:
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
Click to expand...
Click to collapse
It crashed everything on my 8.1 build (and the developer himself recommended me addon-su) maybe a tad harder to use, but at least you learn something at the same time
You should add that the stereo speakers don't work.
Timate5 said:
You should add that the stereo speakers don't work.
Click to expand...
Click to collapse
"Stereo"... When coming from a Nexus 6P this Sally doesn't sound stereo at all... But you're right !
Android Auto doesn't work also on these ROMs. Phone says its incompatible because of some OMX codec issues
timo.helfer said:
Android Auto doesn't work also on these ROMs. Phone says its incompatible because of some OMX codec issues
Click to expand...
Click to collapse
That's too bad, android auto uses h264 streaming codec I think. I think this issue will have something to do with hardware acceleration. Have you tried messing around with the acceleration option found in the developer options to see if it might work?
Nice guide! Thank you @ChriKn!
Can you add to the "Generic AOSP (Android 8.0 and 8.1) by Phhusson"'s part that we need to use A-ONLY version of this rom?
I will try as soon as I have my PC.
Sad news, I got a good opportunity on a Pixel 2 XL and sold my Mate 10 Pro (I need my Pure Android AND Quality Camera)
Does someone want to take the thread over ?
ChriKn said:
I will try as soon as I have my PC.
Sad news, I got a good opportunity on a Pixel 2 XL and sold my Mate 10 Pro (I need my Pure Android AND Quality Camera)
Does someone want to take the thread over ?
Click to expand...
Click to collapse
Sure i can write some impressions. I just installed Carbon ROM.
I did flash but is not booting at all.
Hello, I did everything as mentioned. And phone is not booting it just bootloops.
i can't do a reset is sends me directly back to recovery and just ask to reboot or shutdown phone...
What do I have to do ?
Can i go to stock rom again ?
Thanks
triconix555 said:
Hello, I did everything as mentioned. And phone is not booting it just bootloops.
i can't do a reset is sends me directly back to recovery and just ask to reboot or shutdown phone...
What do I have to do ?
Can i go to stock rom again ?
Thanks
Click to expand...
Click to collapse
Let it Bootloop until it goes to erecovery and than factory reset it
Timate5 said:
Let it Bootloop until it goes to erecovery and than factory reset it
Click to expand...
Click to collapse
I did that but it is just boolooping again, I did all tge steos over and over and it just bootloops every tipe even after factory resete, it actualy asked le once to resete since then after a couole of reboots it goes straight to te erecovery, wherz it ask to login on a wifi to download latest bootloader and rom or reboot or shutdown device...
Info For U Model Bootloader Unlocking Can Be Found
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
Below US snapdragon devices can be bootloader unlocked with above service as long as bootloader version meets below criteria. Bootloader version can be determined from the 5th character from the right on the baseband version or build number, in some cases from kernel version
Below Method is no longer supported if you choose to use the unstable method below you do so on your own
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!
Before Starting This Process Get A USB2 Mini Hub You Are Most Likely Going Too Need It
EXTREME SYNDICATE ROOT METHOD
OEM Toggle Does Nothing On US Model Phones
This root method breaks things and most likely will not be able to be used as a daily driver
You can be on any version bootloader. This will update you to V9 bootloader
This method will work if you are on Android 10 or Android 9 Pie but will put you on Android 8 Oreo. There is no root for Android 10 or Android 9 Pie
You will not be able to use magisk
You will not be able to flash full custom rom like Lineage or any other AOSP roms however GSI system images can be used
You cannot flash custom boot images or recovery images such as regular TWRP
Odin does not work on some later computers with USB 3.1 chip controllers the only work around is using a USB 2.0 mini hub
It is your responsibility to make sure you can use adb properly
Root will break things such as safetynet so deal with it
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!
Notes:
- Safestrap recovery is now available with working MTP while in Safestrap
- This does NOT trip KNOX so don't ask.
- Bootloader is of course still locked.
- This uses some partitions from combo firmware which means 80% battery.
- Each variant will have its own post in its own download section. Download the right stuff!
* Variants this should work on are: N960U/U1/W, G965U/U1/W, G960U/U1/W. If you do not have one of these variants then this forum is not for you!
- Initial files/method will leave you on Oreo stock root.
- It works on latest rev's from rev1 up to the most recent revs.
- As of the initial first release, all variants have an issue with MTP not working except while in Safestrap
- S9 and S9+ also might have some issues with the selfie cam.
- Note 9 @elliwigy
- S9+ @klabit87
- S9 @jrkruse
- Telegram Support Group for All 3: https://t.me/joinchat/DxwvAlhtzHjg4EI9973BGQ
Anything here with a .7z extension will get unzipped before using
Anything here with a .zip extension will get flashed as a zip in safestrap
Anything here with a .tar or .md5 gets flashed in odin
Anything here with a .img extension gets flashed as image in safestrap
Downloads S9 Files:
Safestrap_S9_Cmd_Line.7z
Download S9+ Files:
Safestrap_S9_Plus_Cmd_Line.7z
Download Note9 Files: -- Only For Bit 8 Or Lower
Safestrap_N9_Cmd_Line_Bit8.7z
Instructions to Inject Safestrap:
1. Download and unzip Safestrap_S9__Cmd_Line.7z for your device
2. Plug phone into computer and run Safestrap.exe
3. Follow instructions on screen to enable USB Debugging
4. Then from there the process will be mostly automatic just follow prompts on screen
5. When done flashing BootSwap file you need to hold the buttons to boot to recovery but since we swapped boot and recovery images it will boot system.
Instructions For Flash Rom:
1. Download below files and copy files for rom to phone system img and vendor img and odm zip
Downloads S9 Files:
Stock_Rom_G960.7z
GSI_Rom_G960.7z
Download S9+ Files:
Stock_Rom_G965.7z
GSI_Rom_G965.7z
2. In safestrap flash system img then vendor img and odm zip .
3. Choose data wipe and advance and check data
4.. Now reboot system you will have to hold buttons to reboot to recovery until you see safestrap splash then click continue. 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.
5. 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.
6. Biometrics do not work so don’t try to setup fingerprint or face recognition.
The GSI rom mtp works GSI rom is rooted already just flash phhsupersu.apk found in GSI_Rom zip
If using other GSI roms you have too choose A_Only ones and will probably need to flash the Sh_Remover.zip found in the GSI_Rom zip
ShoutOuts:
@elliwigy For the method and help and everything else
@klabit87 - Ditto
@me2151 - Ditto
@gsm-CHEN - Ditto
@mweinbach - For always posting my achievements on the XDA News portal as well as giving me someone to troll sometimes when bored.
@ShaDisNX255 - He was our best tester, give him credits for testing out GSI as well!
@everyone else I am forgetting!
ENJOY!
Mine
Wow, this is actually pretty good. S9 Snapdragon + treble enabled device? Man, this is going to change everything! I hope something good comes out of this
Does it work on the U/U1 variants of the S9+ as well?
krion64 said:
Does it work on the U/U1 variants of the S9+ as well?
Click to expand...
Click to collapse
It probably will but no files have been made for s9+ yet and not yet tested
Sent from some device I modified
krion64 said:
Does it work on the U/U1 variants of the S9+ as well?
Click to expand...
Click to collapse
It’s confirmed working on both SM-G960U/U1 and SM-G965U/U1
Sent from some device I modified
Any chance that this might be used and not trip knox? This sounds like a similar method that was used in previous devices.
Argyrus said:
Any chance that this might be used and not trip knox? This sounds like a similar method that was used in previous devices.
Click to expand...
Click to collapse
You cannot trip knox on a locked bootloader
Sent from some device I modified
jrkruse said:
You cannot trip knox on a locked bootloader
Sent from some device I modified
Click to expand...
Click to collapse
Gotcha, any idea of when you might get this working for G965U or if you will allow testers?
Argyrus said:
Gotcha, any idea of when you might get this working for G965U or if you will allow testers?
Click to expand...
Click to collapse
Did you not read la couple post above yoir question
Sent from some device I modified
jrkruse said:
Did you not read la couple post above yoir question
Sent from some device I modified
Click to expand...
Click to collapse
I did, but you made two posts, one that you said no files have been created and not tested then also state that it has been confirmed.
Since that seems to be the case then my bad for being confused.
Argyrus said:
I did, but you made two posts, one that you said no files have been created and not tested then also state that it has been confirmed.
Since that seems to be the case then my bad for being confused.
Click to expand...
Click to collapse
When it was tested I posted it was confirmed. Stuff will be released soon
Sent from some device I modified
jrkruse said:
When it was tested I posted it was confirmed. Stuff will be released soon
Sent from some device I modified
Click to expand...
Click to collapse
Awesome, sorry for any confusion.
jrkruse said:
You cannot trip knox on a locked bootloader
Sent from some device I modified
Click to expand...
Click to collapse
jrkruse said:
It probably will but no files have been made for s9+ yet and not yet tested
Sent from some device I modified
Click to expand...
Click to collapse
That means I can have root and have Samsung pay? God damn that makes me wet
Dhdeanha said:
That means I can have root and have Samsung pay? God damn that makes me wet
Click to expand...
Click to collapse
As of right now it's still detecting su binaries. So Samsung Pay probably may not work.
On my G965/U1 I do not even see a "/system/etc/init/init.lab.rc" file on my device, is this because I am updated to the latest Android 9 December 1st security patch?
elguy said:
On my G965/U1 I do not even see a "/system/etc/init/init.lab.rc" file on my device, is this because I am updated to the latest Android 9 December 1st security patch?
Click to expand...
Click to collapse
Don't worry about it. It will work on it, it's been proven to work exactly on Android 9, Dec 2019 security patch.
Wow! that's exciting, I can't wait until this releases. Looks like I'm not updating my phone anymore until then. Especially exciting if it works on Android 9 December 2019 security patch
the question is how likely this will be patched in Samsung's next update and how much time this may cause them to delay their next security patch.
Extreme Syndicate Root for S9 is live!!
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.
NcX 2.5 A71 ROMPretty straight forward, I took OneUI 2.5 firmware, debloated it and added a few features which can be found here: Link to MODs
My plan is to make this the best version of OneUI 2.5 with more features and fixed things (my mission is to fix Secure Folder in the near future) Fixed
Anyway, let's get started.
Code:
Your warranty is now void.
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about flashing this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. HARD!
Features!
TWRP Included
Full OneUI 2.5 features
Debloated
Added camera features
Dolby Atmos without earphones
Optimized
Edge Lighting fully enabled
Secure Folder fixed
Smart View fixed
Samsung Health fixed
Samsung OCR service
Bugs!
Secure Folder broken (will try to fix later) Fixed on 2.5.1
Samsung Pass broken (because of knox 0x1, duh) Removed from ROM, it will never work.
Bug with AOD brightness when you use fingerprint unlock method. This bug happens when you have AOD to always show. If AOD is showing, then you turn the screen on to only show lockscreen clock and then turn the screen off for AOD to show, the brightness of AOD will reduce to the most minimal and it will be hard to see, regardless of what brightness you set up. There are 2 ways to getting rid of this bug:
Disable unlocking phone with fingerprint
Unlocking your phone and then locking it again. This will only fix it until you trigger the bug again
Fixed, clock animation removed.
You tell me
Changelog!
25/Oct/2020 (NcX 2.5.2):
Added 60 fps recording on selfie cam
Added wide selfies. (a biiiiit buggy, but serviceable)
Added 24 fps recording modes on pro video mode
Fixed Samsung Health
Added Samsung OCR Service for better text extraction
12/Oct/2020 (NcX 2.5.1):
Secure Folder fixed
Smart View fixed
AOD bug fixed
Removed Samsung Pass
Removed Samsung Daily
Removed "Tips" app
Removed Bixby
Added camera features
08/Oct/2020: Release
Links!
(V2.5.2)Google Drive
(V2.5.1)Google Drive
(V2.5)Google Drive
PrequisitesMANDATORY ALWAYS: SD Card. It IS possible to have it on internal storage but ONLY if you are not encrypted. If you are encrypted, then you will need to FORMAT DATA and that will delete everything in your internal storage and you won't be able to add it back to internal storage with TWRP because MTP is broken.For installing 2.5.1/2.5.2:
Installing and following NcX 2.5 installation steps, as well as its prequesites
TWRP Installed (included in NcX 2.5)
Download multidisabler.zip (link: From Telegram Group (also attached on this thread) and add to SD Card or internal storage
Download Magisk zip installer to your SD Card or internal storage
For installing 2.5:
Update to bootloader U3 (either install OneUI 2.1 or OneUI 2.5 fully with Odin), otherwise you will have problems with camera
Fully unlock bootloader. I don't mean just turning OEM unlock on in developer settings , I mean FULLY unlock. If you didn't know, Samsung changed up how you unlock the bootloader on newer devices like this one. @topjohnwu gets a little more specific here: Explanation but I'm going to quote the important stuff to FULLY unlock bootloader:
Unlocking BL on modern Samsung devices have some caveats, so I figure this would be helpful.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: reboot and press the download mode key combo for your device.
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
Go through the initial setup. Skip through all the steps since data will be wiped again later.
Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode.
Click to expand...
Click to collapse
Download Magisk zip installer to your SD Card or internal storage
Download multidisabler.zip (link: From Telegram Group and also attached in this thread) and add to SD Card or internal storage
Instructions!For installing 2.5.1/2.5.2:
Reboot to TWRP
Flash NcX 2.5.1.img or NcX 2.5.2 as "super" image in TWRP
Reboot to Recovery
Format data if you are coming from Stock ROM. If you are coming from NcX 2.5 then you don't need to wipe or format, you can just skip this step.
Flash multidisabler (this is required always)
Flash Magisk zip (optional)
Reboot and wait patiently
For installing 2.5:
Reboot to download mode and add AP_NcX 2.5 A71 in AP on Odin
Uncheck the Auto reboot option in Odin
Flash
When it is finished, force a manual reboot (keep pressing VOL - and Power buttons together)
Immediately when phone reboots, boot to recovery mode (VOL + and Power button)
If your phone was unencrypted before, just do a normal wipe. If your phone was not unencrypted before, do a full data format (Go to WIPE option in TWRP, select FORMAT DATA button at the bottom and they type yes on the keyboard. This will completely wipe your internal storage so be sure to backup and photos, music, etc... you have in internal media.)
Flash multidisabler to ensure you do not get encrypted
Flash magisk (I don't know if this is mandatory, I would fully recommend it though)
Reboot and wait patiently
Credits! @ananjaser1211 for all your help and always willing to lend a helping hand
@SuperR. For his Super R's Kitchen which you can find here: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
@topjohnwu for Magisk
@sac23 for his tutorial on how to fix Secure Folder which you can find here: https://forum.xda-developers.com/showpost.php?p=82978861&postcount=1522
@Belco02 for the extra camera modes and features
@ianmacd in Telegram group TWRP/Root Samsung Android Devices for compiling TWRP for us
@ Samsung for the firmware
@ Team TWRP for their amazing recovery
@ To users like you!
If you feel I missed you, please give me a PM so I can add you
XDA:DevDB Information
NcX 2.5 for A71, ROM for the Samsung Galaxy A71
Contributors
ShaDisNX255, Ian Macdonald
Source Code: https://github.com/ianmacd/twrp_a71
Source Code: https://github.com/ianmacd/a71
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: OneUI 2.5
Version Information
Status: Stable
Current Stable Version: 2.5
Stable Release Date: 2020-10-08
Created 2020-10-08
Last Updated 2020-10-08
Join our Telegram group
Code:
Check out the latest projects on our Telegram group, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA
Link: Telegram Group
Join our Discord group
Code:
Check out the latest projects on our Discord, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA
Link: Discord
Android group in spanish
Link: Grupo Android
FAQ
[Q] My phone is stuck in bootloop/infinite boot, what should I do?
[A] It is normal for first instalation to take aprox 10-20 minutes on first boot, let it sit for a little bit
[Q] Even after 20 minutes, my phone is still in a bootloop/infinite boot, what can I do?
[A] It is possible that your previoius Android setup is conflicting with this new setup. Please, do the following:
1. FORMAT DATA (not WIPE, FORMAT!)
2. Try the instalation of NcX again
[Q] I've found a bug, what should I do
[A] Please read the "Bugs" section of the thread to see if your bug has been reported, if it hasn't, please let me know exactly what the problem is so I can take a look
[Q] I flashed magisk on TWRP but no apps are asking for SU Permission
[A] Make sure you have the Magisk Manager app installed
[Q] I don't see Magisk Manager in my apps
[A] You need to download the manager from the official source: https://github.com/topjohnwu/Magisk
[Q] Something bothers me and I want it fixed/changed
[A] Please, kindly make a request and if it's within my grasp, I'll try to fix it. Just, don't be rude and demand something. Either that or return to stock, your choice
How to report a bug/Ask for a change
Over the small amount of time I've been doing my edits and shared them with the community, I've noticed something that seems to irritate me. I can't speak for all the developers on this forum, but I do edits/ROMs/PORTs/etc... to what I like. I don't work for anybody else but me. I share my work because it may have something of value to other people and/or some people may share the same taste as me on regards to what they want on a ROM.
That being said, that doesn't mean I will completely ignore what the community has to say.
First and foremost, it must be said, I am merely a beginner. I do not claim to be a professional developer that knows how to add everything, I am nowhere close and I learn as I go.
There are ways to ask for something and/or report a bug when it comes to ROMs, and this post is my attempt to try to explain how to (and how not to) report a bug in order to help me out as much as possible to try to fix something
You can also ask for something to be added, but there are also ways to ask for something
So, here we go
Keep in mind:
I do not add stuff that can easily be downloaded from the Playstore
I, myself, don't do kernel edits
I COULD remove stuff if NOBODY uses it
---REPORTING BUGS---
How NOT to report a bug:
"SystemUI (or any app)is crashing, please help!"
"Instagram doesn't allow me to edit my post, what could be wrong?"
"My bank account app is not letting me do such thing"
These posts are sort of pointless as they only state something but I have no context on what could be causing it. Also, I can't really control (for the most part) third-party apps, so if you're going to ask about them this way, don't even bother
A slightly better way to report a bug:
"I clean installed the ROM and was working fine, after I installed Facebook and logged in, I immediately uploaded a photo and SystemUI started to crash. Can you look in to it?"
"I tried to install Black Neon theme (a link to it would work as well) and it was working fine until I tried to activate AOD (or anything else for some reason) and SystemUI (or any other app) is crashing, could you look in to it?"
"My bank account app doesn't let me take a screenshot of my accounts. I get a toast notification saying "Can't take screenshot due to security policy"
As you can see, this provides a bit more context and explanation on your current situation. This gives me a little more detail on trying to replicate the problem and hopefully could fix it by replicating it. Well, except for point #3 which is out of my hands for the most part (I think). If you include what kernel you're using would make everything better! Also any significant change that would require root (like xposed and or anything that modifies /system also needs to be informed for better results)
The BEST way to report a bug:
LOGCAT!!!!!!!!!!!!!!!!!!
Please learn the ins and outs of a logcat, this really helps a lot on finding what the problem is. Also, please give a brief explanation as the above examples when providing a log cat
---ASKING FOR STUFF TO BE ADDED---
How NOT to ask for stuff:
On your next update, add iris scanner
You should add (app) on your next update
Hey, please add (app or feature) on your next update
No, I do not work for you. Even if you say please like the third example, that doesn't mean you're being polite. It still sounds like an order lol so you should probably rephrase your request.
How to ask for stuff to be added to my work:
Would you be so kind to add (feature) to your ROM, if possible?
Would it be possible to add this app to your ROM?
Please, can you add (feature) to your ROM, if it isn't much to ask?
See how politeness makes everything better? You're not demanding it, you're just politely asking to see if maybe it is within my grasp to add something. And if all request would be like this, I can assure you I'd try my best to add said feature
I hope this is useful to you or I at least hope that some people read it.
If not, I can just tell you to return to stock ROM, probably better than any ROM I put out anyway
Enjoy guys, keep on the lookout for updates. I plan on adding more MODs and fixes
Attach the singletake .xml also here
sankhauaa said:
Attach the singletake .xml also here
Click to expand...
Click to collapse
I'll hold it off.
Plan on adding a future update with this and more stuff included
Good mod! Downloading...
well done mate, nice to see
New update hopefully tomorrow.
What's new?
-Fix Secure Folder, now working
-Fix Smart View mirroring, now working
-Adding CSC features, in progress
When i try to do the process of unlocking again It say after long press volume up. Lock Bootloader? Guess thats not what i want? My device is rooted stock with twrp installed..... Do you have an idea.?
I want to install your rom.
hans3103 said:
When i try to do the process of unlocking again It say after long press volume up. Lock Bootloader? Guess thats not what i want? My device is rooted stock with twrp installed..... Do you have an idea.?
I want to install your rom.
Click to expand...
Click to collapse
If you've already rooted, that means you have fully unlocked bootloader and it means that you can now freely install my ROM.
I installed it, it look very good. Its a big timesaver also. I used to root this device in a time comsuming way. This rom is very easy.... Very nice work!
hans3103 said:
I installed it, it look very good. Its a big timesaver also. I used to root this device in a time comsuming way. This rom is very easy.... Very nice work!
Click to expand...
Click to collapse
Thanks, next version will be easier to flash, just with super.img flash on TWRP.
ShaDisNX255 said:
Thanks, next version will be easier to flash, just with super.img flash on TWRP.
Click to expand...
Click to collapse
I will try it for sure, can I do an update or do I have to make a clean install?
hans3103 said:
I will try it for sure, can I do an update or do I have to make a clean install?
Click to expand...
Click to collapse
It can be installed with current version so no need to wipe data
ShaDisNX255 said:
It can be installed with current version so no need to wipe data
Click to expand...
Click to collapse
Very nice....many thanks!
nice business friend
Even if resizing in vendor, it will be nice because it will be very possible to make mod and custom kernel
No idea
my galaxy a71 its still in bootloop. bootloader fully unlocked with oem activated. data formated, installed decrypted data, and magisk zip installed, pls help..
zorexblade said:
my galaxy a71 its still in bootloop. bootloader fully unlocked with oem activated. data formated, installed decrypted data, and magisk zip installed, pls help..
Click to expand...
Click to collapse
Are you getting to boot animation?
Were there any red messages in TWRP when you were installing?
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Articul8Madness said:
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Click to expand...
Click to collapse
Hi. I appreciate a lot your efforts. I know the feeling when you progress with stuff like this. I'm sorry I have no time in these months to assist. Anyway, I hope you'll manage to go forward with this. Keep up with the good work.
useless789 said:
Hi. I appreciate a lot your efforts. I know the feeling when you progress with stuff like this. I'm sorry I have no time in these months to assist. Anyway, I hope you'll manage to go forward with this. Keep up with the good work.
Click to expand...
Click to collapse
CAn you at least tell me how to port a TWRP on Android 10? Can't find any useful information with the new filetypes.
Articul8Madness said:
CAn you at least tell me how to port a TWRP on Android 10? Can't find any useful information with the new filetypes.
Click to expand...
Click to collapse
I'm not sure what you mean by filetypes. Do you mean the A/B partitions (and the fact that there's no separate recovery partition) or something else?
Articul8Madness said:
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Click to expand...
Click to collapse
This is tremendously amazing work. TWRP would be a killer feature with the 5G Ace. Couple that with Lenovo having released the source code, and this forum may get popping again!
useless789 said:
I'm not sure what you mean by filetypes. Do you mean the A/B partitions (and the fact that there's no separate recovery partition) or something else?
Click to expand...
Click to collapse
I was referring to the super_sparsechunk type files that when you look at their "filetype" it has 0 image by its name if its super_sparsechunk.0, 1 if its super_sparsechunk.1 and the like. This is different than the old basic img files that read .img. This is where the learning curve for me kicks in.
Articul8Madness said:
I was referring to the super_sparsechunk type files that when you look at their "filetype" it has 0 image by its name if its super_sparsechunk.0, 1 if its super_sparsechunk.1 and the like. This is different than the old basic img files that read .img. This is where the learning curve for me kicks in.
Click to expand...
Click to collapse
I see. Thanks for the explanation. I'm not sure if this could help, but a quick search on google led me to this (a bit old) video:
I'm really busy until the end of the month so I can't really dedicate my time to this stuff though I would love to.
useless789 said:
I see. Thanks for the explanation. I'm not sure if this could help, but a quick search on google led me to this (a bit old) video:
I'm really busy until the end of the month so I can't really dedicate my time to this stuff though I would love to.
Click to expand...
Click to collapse
I see you already tried this here: Post in thread '[Tool] SparseConverter v1.0.1' https://forum.xda-developers.com/t/tool-sparseconverter-v1-0-1.2749797/post-84767377
If I manage I'll take a look at this asap.
useless789 said:
I see you already tried this here: Post in thread '[Tool] SparseConverter v1.0.1' https://forum.xda-developers.com/t/tool-sparseconverter-v1-0-1.2749797/post-84767377
If I manage I'll take a look at this asap.
Click to expand...
Click to collapse
Any and all contributing help is appreciated!
@Articul8Madness I managed to combine the sparse chunk files into a raw image file. I also managed to mount the image, but only in read-only mode. I'll post with updates as I get passed this obstacle.
Seems the US version of this phone isn't popular enough for dev support...oh well I have R/W access so I was able to delete system app bloatware and I have xposed installed. Stock Reteu firmware is working perfectly on Metro...good luck everybody.. I'm looking for a new 5G phone..
Unfortunately, there are no developers here.
All we can produce is a ported twrp where the touchscreen does not work.
The touchscreen does not work due to problems with the porting tool and the smartphone.
I heard that if you build it from source yourself, it will work.
But I can't find any tutorials for android 10+ and I don't even know what files I need.
PEACH-PIT said:
Unfortunately, there are no developers here.
All we can produce is a ported twrp where the touchscreen does not work.
The touchscreen does not work due to problems with the porting tool and the smartphone.
I heard that if you build it from source yourself, it will work.
But I can't find any tutorials for android 10+ and I don't even know what files I need.
Click to expand...
Click to collapse
I posted the source code. The guys over on the Moto One 5G know what tools you need. I was using Carliv's kitchen to build but I've never built before - they had the same problem as us with the touchscreen and had to make modules. That counts me out because that's above my paygrade, lol.
Articul8Madness said:
I posted the source code. The guys over on the Moto One 5G know what tools you need. I was using Carliv's kitchen to build but I've never built before - they had the same problem as us with the touchscreen and had to make modules. That counts me out because that's above my paygrade, lol.
Click to expand...
Click to collapse
Not entirely sure what you mean. If your doing some kind of frankenstein recovery, I'm sure you just failed to copy some module or firmware, obviously the ts works in the official software.
1.) Find out what touchscreen chipset your device uses (you can use kernel log or system info apps or whatever)
2.) Determine which kernel module supports it (all modules built will be in your kernel config)
3.) modprobe that module from adb in your recovery. If it doesn't just work, you will receive some error on the command line or dmesg that you can use to fix it. Could need a configuration file or something, idk. It's likely an opensource module that you can read through and I bet you can find specific info online since your not the first to hit this issue.
If your wondering how to build the kernel, I can help a little, but it's incomplete:
Kernel source:
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
github.com
Build instructions:
readme/MMI-QPN30.33-40.txt at master · MotorolaMobilityLLC/readme
Readme's for motorola builds. Contribute to MotorolaMobilityLLC/readme development by creating an account on GitHub.
github.com
Snapdragon LLVM Toolchain:
snapdragon-llvm-8.0.6-linux64.tar.gz
drive.google.com
Retail config is on your device:
/proc/config.gz
The instructions don't cover the qcom toolchain, you just take the files here:
snapdragon-llvm-8.0.6-linux64.tar.gz/toolchains/llvm-Snapdragon_LLVM_for_Android_8.0/prebuilt/linux-x86_64/*
and place them here:
$my_top_dir/vendor/qcom/proprietary/llvm-arm-toolchain-ship/8.0/
When building, skip the cat command, and place your config manually to $kernel_out_dir/.config
The step I haven't done is build a device tree. It's not that it's too difficult, I just haven't put in the time required to do it. It's not strictly necessary to achieve for my goals since I only wanted modules and know how to patch the kernel to be able to use them.
https://github.com/moto-sm7250/android_device_motorola_kiev/tree/android-10
Will this not work?
I do not know how to build it.
fddm said:
Not entirely sure what you mean. If your doing some kind of frankenstein recovery, I'm sure you just failed to copy some module or firmware, obviously the ts works in the official software.
1.) Find out what touchscreen chipset your device uses (you can use kernel log or system info apps or whatever)
2.) Determine which kernel module supports it (all modules built will be in your kernel config)
3.) modprobe that module from adb in your recovery. If it doesn't just work, you will receive some error on the command line or dmesg that you can use to fix it. Could need a configuration file or something, idk. It's likely an opensource module that you can read through and I bet you can find specific info online since your not the first to hit this issue.
If your wondering how to build the kernel, I can help a little, but it's incomplete:
Kernel source:
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
github.com
Build instructions:
readme/MMI-QPN30.33-40.txt at master · MotorolaMobilityLLC/readme
Readme's for motorola builds. Contribute to MotorolaMobilityLLC/readme development by creating an account on GitHub.
github.com
Snapdragon LLVM Toolchain:
snapdragon-llvm-8.0.6-linux64.tar.gz
drive.google.com
Retail config is on your device:
/proc/config.gz
The instructions don't cover the qcom toolchain, you just take the files here:
snapdragon-llvm-8.0.6-linux64.tar.gz/toolchains/llvm-Snapdragon_LLVM_for_Android_8.0/prebuilt/linux-x86_64/*
and place them here:
$my_top_dir/vendor/qcom/proprietary/llvm-arm-toolchain-ship/8.0/
When building, skip the cat command, and place your config manually to $kernel_out_dir/.config
The step I haven't done is build a device tree. It's not that it's too difficult, I just haven't put in the time required to do it. It's not strictly necessary to achieve for my goals since I only wanted modules and know how to patch the kernel to be able to use them.
Click to expand...
Click to collapse
This recovery I built in this thread I used Hovatek's tool to do. I have never built a recovery and I was hoping if someone got the ball rolling we could get a dev to jump in. That hasn't happened.
The guys with the other variant of this phone said they had to create modules. Go to the Moto One 5G forums and see the thread. They had the same problems too, but they had more dev support than we do.
I have never built a TWRP, let alone from source, so half of what you sent I have no idea what it is or how to decompile it (yet).
I have posted the entire Kernel Motorola released its in the other thread. The Device Tree is official and out on github.
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
useless789 said:
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
Click to expand...
Click to collapse
Is this the correct twrp for this phone?
Root Motorola One 5G Ace XT2113 and Install TWRP Recovery 3.5.0
Easy tutorial to Root Motorola One 5G Ace XT2113-2, XT2113-3, XT2113-5 easily. For rooting, you have to flash TWRP Recovery 3.5.0 on Android 10 through guide.
www.androidweblog.com
Later guys, keep up the good work
Tomspector said:
Is this the correct twrp for this phone?
Root Motorola One 5G Ace XT2113 and Install TWRP Recovery 3.5.0
Easy tutorial to Root Motorola One 5G Ace XT2113-2, XT2113-3, XT2113-5 easily. For rooting, you have to flash TWRP Recovery 3.5.0 on Android 10 through guide.
www.androidweblog.com
Later guys, keep up the good work
Click to expand...
Click to collapse
This is a fake. It's non-functional garbage.
There is no harm in trying it, unless you flash it, but there is no need to try it.
useless789 said:
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
Click to expand...
Click to collapse
I have a request to the developers.
GitHub - moto-sm7250/android_device_motorola_kiev at android-10
DT for Moto G 5G / One 5G Ace. Contribute to moto-sm7250/android_device_motorola_kiev development by creating an account on GitHub.
github.com
Can you please build this twrp?
I'm trying to build it.
But I don't know how to solve the error.
I don't think I can build it.