Related
Hello guys,
I don't see a dedicated section for lenovo Z5s but I managed to download the TWRP 3.3.1 from baidu (only chinese and english but chinese default).
I then looked for rom authors, it seems they all are using chinese custom roms, anyway they are mirrored and MIUI has been tested by me.
I decided to mirror all downloads I found (they were quite hard to get):
TWRP :
TWRP-3.3.1-LENOVO_Z5S-CN-wzsx150-fastboot.7z (with fastboot instructions and files)
TWRP-3.3.1-0529-LENOVO_Z5S-CN-wzsx150.zip (can be flashed with TWRP)
recovery-TWRP-3.3.1-0529-LENOVO_Z5S-CN-wzsx150.img (only .img file)
Chinese Roms :
Z5s_miui_19.5.20(9.5.16)_Pie_Public_by Art_Chen(TWRP_FASBOOT_2in1).zip
Z5S_H2OS_190722
Z5s_Flyme7.3.1.0A_YouLinw_V1.5_19.07.25
GSI Roms : (Seems to be AB, because A-Only are not working)
According to 4PDA, only Pixel Experience have been tested for now, they provide screenshot and video.
Pixel Experience GSI Tested working!
Ressurection Remix Tested working!
Arrow OS Tested Working!
All other public GSI images (tested many, none of them working, no idea why)
Official ROM backup (QPST format):
https://mirrors.lolinet.com/firmware/lenovo/l78071/
I added permissiver v4 I got from Telegram on Android Q GSI channel
Instructions for GSI Images (thanks to 4PDA):
Using TWRP recovery:
0. Download the firmware files to your smartphone.
1. Enter the recovery menu. To do this, turn off the smartphone and simultaneously hold down the power button and volume +.
2. In the recovery menu, select the item Cleaning -> Selective cleaning. Check the boxes on Dalvik / ART Cache , System , Data and Cache . Swipe the slider to the right. Return to the main recovery menu.
3. In the main recovery menu, select Installation -> Install Img. Select firmware file XX.img. For system section firmware, select System Image, and for boot - Boot. Swipe the slider to the right. Go to the main recovery menu. Select Reboot -> System.
This procedure is new for all smartphones, so don't be afraid to ask questions if something went wrong.
Click to expand...
Click to collapse
Using adb:
0. Install the USB, ADB and Qualcomm drivers on the PC. Reboot the computer and connect the smartphone to the PC. Download files for firmware on PC.
1. In the folder where the files (.img) were saved, press SHIFT and the right mouse button from scratch. In the context menu, select PowerShell or CMD (activate command console).
2. Enter the commands one by one
fastboot flash system XX.img
fastboot erase userdata
fastboot -w
fastboot reboot
PS In some cases, it will be necessary to flash vendor and / or boot:
fastboot flash vendor XX.img
fastboot flash boot XX.img
Click to expand...
Click to collapse
Source for TWRP: https://club.lenovo.com.cn/thread-5442053-1-1.html
Source/author for H2OS & Flyme : Weibo
Source/author for MIUI : Weibo
4PDA page : https://4pda.ru/forum/index.php?showtopic=960895
Please move topic to another section if wrong.
First, thanks for the Thread. Very informative.
let me report that H2OS showes black screen after boot logo,
Flyme seems working but with some minor problems (bad english translation, no google apps on built-in chinese app store, upper notification bar not aligned, etc).
TASON42 said:
First, thanks for the Thread. Very informative.
let me report that H2OS showes black screen after boot logo,
Flyme seems working but with some minor problems (bad english translation, no google apps on built-in chinese app store, upper notification bar not aligned, etc).
Click to expand...
Click to collapse
Hi, thanks. H2OS is the only one i have not tested, i will remove the link. If you live outside Cina I would recommend GSI rom since chinese roms might have issues with notifications.
I now recommend AEX (arm64 AB)
vickdu31 said:
Hi, thanks. H2OS is the only one i have not tested, i will remove the link. If you live outside Cina I would recommend GSI rom since chinese roms might have issues with notifications.
I now recommend AEX (arm64 AB)
Click to expand...
Click to collapse
Don't you lost WIFI after flashing just GSI img file? I need to flash MIUI before flashing any GSI to keep WIFI working.
and this maybe is a lil bit off topic but have you ever had problems with fastboot?
my fastboot is not working properly since I bought this smartphone, 'fastboot devices' works but
can't flash anything, saying random error like 'maxium download size not reported', 'too many links', and even 'error: no error'...
tried changing usb port, cable, driver, everything I can think of.
I can still flash boot.img, recovery.img, vbmeta.img via QFIL but I want to use fastboot which is less hassle..
Report:
MSM Xtended is working too.
problems I hav till now.
1. WIFI not working if you flash directly from ZUI, or wipe cache/dalvic.
2. loud speaker sound problems at various ROMs, with or without equalizer app.
3. notch size is not matching with status bar at every ROMs
4. double tap to wake is not working for every ROMs.
I actually did flash miui first.
I contacted art_chen to get international MIUI, he told me he dont have phone anymore but we can download his miui zip and replace system.img with the one official from MI9 (taking the system.img full global fastboot firmware and it should work).
The vendor image and boot.img included in the miui rom have been customised by art_chen so he probably fixed wifi !
Since i also dont have the phone i cannot test so well.
vickdu31 said:
I actually did flash miui first.
I contacted art_chen to get international MIUI, he told me he dont have phone anymore but we can download his miui zip and replace system.img with the one official from MI9 (taking the system.img full global fastboot firmware and it should work).
The vendor image and boot.img included in the miui rom have been customised by art_chen so he probably fixed wifi !
Since i also dont have the phone i cannot test so well.
Click to expand...
Click to collapse
1. did you had loud speaker problem after flashing treble GSI files? Mine distorts heavily with every .img file i tried.
2. I'm testing swapping .img file with other xiaomi devices but none of them is working. Sounds like you don't own the device anymore so this will be lonely fight.
---------- Post added at 03:41 AM ---------- Previous post was at 03:36 AM ----------
I need FM radio which is not included in Art_chen's ROM so I tried swapping system.img with Redmi note 7 (closest spec), and failed.
TWRP log is saying "Failed to mount '/system_root'" so i guess the reason is partition chart problem or pre-installed magisk, I'm not sure I can fix this but I'll keep trying.
since FM radio is not even on the hardware list so i decided to give up FM radio, but updating android security patch with
Mi 9 (since OP mentioned), Mi 9 SE (quite close spec) and Mi CC9 (not international but even closer than redmi note 7) firmware files,
I don't think any of them would work, but I'll keep trying(2).
You could also try with Flyme blobs (boot, vendor etc) they are from different dev
If you messed up partition i recomment flash wjole miui or flyme with adb
Looking for Global Rom
I purchased the Chinese version of this model.
I tried various GSIROMs, but there were a lot of things that didn't work.
I want to use ZUIOS obediently. Does anyone have a Global Rom?
Also, you should be careful about overwriting GSIROM.
The lighting adjustment has gone wrong.
(No problem with genuine ROM)
teketake said:
I purchased the Chinese version of this model.
I tried various GSIROMs, but there were a lot of things that didn't work.
I want to use ZUIOS obediently. Does anyone have a Global Rom?
Also, you should be careful about overwriting GSIROM.
The lighting adjustment has gone wrong.
(No problem with genuine ROM)
Click to expand...
Click to collapse
there is no Official Global Firmware since this phone is only for china mainland. You can enable google service/calendar/GPS by downloading play store .apk from lenovo app store.
there is faulty firmware chimera with chinese rom + google service preinstalled, but trust me, it is unusable. It has every unfamiliar chinese-specific settings + bunch of 'google service force closed' alarms, bad battery drain by google service, crashing app downloading, etc.
Yes, I'm still using this mediocre device, found some useful articles about GSI, will throw links here.
https://www.dospy.wang/forum.php?mod=viewthread&tid=1626&extra=page=1
https://www.htcmania.com/showthread.php?t=1504540
it's not in English but google translate will help you guys.
here's the essence.
Flash MIUI first, its mandatory. Without it you will lost WiFi.
But, you will lost DT2W and FM radio at kernel level if you flash MIUI.
Now you can flash any GSI, but I recommend Pixel Experience from the link I uploaded,
because fixes of common GSI issues like statusbar height (use magisk+rirucore+riruedxposed+gravitybox), sound distortion (use magisk+audio compability), headphone not detecting (random) are integrated to the GSI.
Global ROM was uploaded to 4PDA.
K10 note is almost identical with Z5s and now it's Global released, you can get the QFIL files, I guess just swap system.img and userdata.img might work.
the difference between Z5s chinese ROM and K10 note global ROM must be something like that of Z6 pro chinese and global version...
edit: yes it is working, just swap system_xx.img and userdata_xx.img files will do the work, only camera.apk won't work properly (no optical zoom just digital, ramdom crash sometimes ) but we can stick with Gcam port.
I flash pixel experience then i find out auto brightness isn't work well.i adjust it to the lowest , but it still so bright.how can i fix it?
H2OS 9 : https://mp.weixin.qq.com/s/45L1TZFa0g1MP3-jSYhMDg
Flyme 8 : https://mp.weixin.qq.com/s/P8tL8eq9UhV8Hbq8-7nYBQ
MIUI 11 : https://mp.weixin.qq.com/s/q-8qnFI1VP8upyz6quZZmw
it's all from YouLinw, the dev of Flyme 7 port in OP.
Flyme 8 is still in daily alpha, it boots but stuck in Terms&Conditions screen.
MIUI 11 and H2OS works great, (but don't use pre-installed Magisk, install official v19.3 from via TWRP. idk why but pre-installed one or lastest v20.1 won't work.)
Android Security Patch in MIUI11 is Sep 1st while H2OS is Aug 1st (same with PE I linked before)
so it's your choice to use MIUIsh MIUI with newer ASP, or H2/PE which is more stock android, but with older ASP.
Quack phh Android 10 is not working sadly,
neither vendor by Art_Chen (MIUI10) nor YouLinw booted,
with original vendor it boots but Wi-Fi won't work, like always.
---------- Post added at 04:29 AM ---------- Previous post was at 04:21 AM ----------
s94084sammy said:
I flash pixel experience then i find out auto brightness isn't work well.i adjust it to the lowest , but it still so bright.how can i fix it?
Click to expand...
Click to collapse
I have the same problem, I just bear it since it's not major one. you can use any third party apps from play store that dims your screen if you want to.
Hello, i think about buying this phone or xiaomi note 7 pro . Want to flash lineage or aosp base rom, someone has a point of view about best hardware and best dev support ? For me note 7 pro have better dev support but one week for unlock bootloader and lcd cheaper for repair . Can't find photo versus, z5s have three module but rn7p have 48mp , someone have an advice ?
bretzelpopo said:
Hello, i think about buying this phone or xiaomi note 7 pro . Want to flash lineage or aosp base rom, someone has a point of view about best hardware and best dev support ? For me note 7 pro have better dev support but one week for unlock bootloader and lcd cheaper for repair . Can't find photo versus, z5s have three module but rn7p have 48mp , someone have an advice ?
Click to expand...
Click to collapse
I think Redmi Note 7 pro is the buy.
I chose Z5s because of its cheaper price, lighter weight, and more premium material (alu+glass).
And I also had nice Dev experience with ZUK Z2 so I expected the same with this phone (which was wrong guess )
Cam, I assume stock camera is better in Z5s, but You won't use stock ZUI/MIUI ROM anyway so that won't bother you.
GCam works great on both model, ported stock camera apk won't work as good as it's on stock ROM, both in Z5s/Note 7.
Sound, both mediocre.
Screen, both mediocre (HDR on Z5s is fake color boost only for chinese content apps),
and Z5s has unusual copper plate type connection not like normal ribon cable.
Dev, Z5s is for China mainland only so you won't get proper global/AOSP ROM developments,
but you can get bunch of MIUI/Flyme/H2OS ROMs...
Official Update is also better in MIUI over ZUI.
Hi there. Was there any AOSP or LineageOS working on our Z5S?
Hi @vickdu31 do you have a copy of recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img ? I tried as a guest in 4pda but I get a 404 error. Thanks for your help!
carlshark said:
do you have a copy of recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img?
Click to expand...
Click to collapse
https://drive.google.com/file/d/1-JwD0Ie5xY2CQRDv8rvZMK6ICf0vmp4n/view?usp=drivesdk
Proof of concept - I've successfully booted my own LineageOS GSI on A60 (which is identical to M40 in terms of hardware); other PHH-based GSIs should work as well.
Procedure? Just pack your favorite ARM64 AB GSI image into a .tar and flash via Odin. It's that simple (to at least make it boot).
As far as I've discovered, bugs are 1) bad manual brightness behaviour (can be fixed similarly to this - the command to use here is "setprop persist.sys.phh.samsung_backlight 2"), 2) calls are always in speaker mode, 3) MTP is broken (can be fixed with a modified stock kernel in the future) and 4) no VoLTE as with all GSIs.
If you install one now, there's no navbar on boot, and statusbar doesn't account for the hole-punch either, but I've already submitted a device overlay to PHH, which should fit both A60 and M40. GSIs built afterwards should look better (like in the screenshot, where I already applied the overlay).
With no TWRP available, setup can be tough, but overall it's pretty refreshing to see AOSP-based stuff running on this device.
As a m40 user it sounds me great and left hope for my device.. looking foreword to it
dear AndyYan, could you provide links(to twrp and GSI themselves) or something?
sorry. no need of providing. I misunderstood
Great!
Great Work buddy. Hope you make progress and soon have a smooth GSI on your device :good:
AndyYan said:
Proof of concept - I've successfully booted my own LineageOS GSI on A60 (which is identical to M40 in terms of hardware); other PHH-based GSIs should work as well. .....
.....With no TWRP available, setup can be tough, but overall it's pretty refreshing to see AOSP-based stuff running on this device.
Click to expand...
Click to collapse
Hey, when im trying to flash with odin (AP), the app has just shutted down. What's the correct way to install?
Even tho, app for checking treble says me, that i have A-only while you say youve flashed AB
MediaNik said:
Hey, when im trying to flash with odin (AP), the app has just shutted down. What's the correct way to install?
Even tho, app for checking treble says me, that i have A-only while you say youve flashed AB
Click to expand...
Click to collapse
My bad, I forgot to mention that the image has to be renamed to system.img.ext4 before packaging.
We're A-only but system-as-root. Images for system-as-root are named AB for historical reasons.
AndyYan said:
My bad, I forgot to mention that the image has to be renamed to system.img.ext4 before packaging.
We're A-only but system-as-root. Images for system-as-root are named AB for historical reasons.
Click to expand...
Click to collapse
it is being flashed, but when it's done, it goes in download mod, displays small red exclamation mark and says "reason system: error validating footer"
MediaNik said:
it is being flashed, but when it's done, it goes in download mod, displays small red exclamation mark and says "reason system: error validating footer"
Click to expand...
Click to collapse
Then probably dm-verity kicking in (weird, how come when we've unlocked BL already).
I installed Magisk beforehand (patch AP), try it yourself.
Can you make please more detailed guide how to flash it
Because when I try, it gives me error
AndyYan said:
Proof of concept - I've successfully booted my own LineageOS GSI on A60 (which is identical to M40 in terms of hardware); other PHH-based GSIs should work as well.
Procedure? Just pack your favorite ARM64 AB GSI image into a .tar and flash via Odin. It's that simple (to at least make it boot).
As far as I've discovered, bugs are 1) bad manual brightness behaviour (can be fixed similarly to this), 2) calls are always in speaker mode, 3) MTP is broken (can be fixed with a modified stock kernel in the future) and 4) no VoLTE as with all GSIs.
If you install one now, there's no navbar on boot, and statusbar doesn't account for the hole-punch either, but I've already submitted a device overlay to PHH, which should fit both A60 and M40. GSIs built afterwards should look better (like in the screenshot, where I already applied the overlay).
With no TWRP available, setup can be tough, but overall it's pretty refreshing to see AOSP-based stuff running on this device.
Click to expand...
Click to collapse
can you please tell me how to do that?
deadinside322 said:
Can you make please more detailed guide how to flash it
Because when I try, it gives me error
Click to expand...
Click to collapse
tomznottomo said:
can you please tell me how to do that?
Click to expand...
Click to collapse
So slightly more details:
1) Make sure Magisk is properly installed (patch AP) and running on your device first, likely because we need it to disable dm-verity
2) Download any ARM64 AB GSI and rename the image (*.img) to system.img.ext4
3) Pack it into tar format (e.g. 7-zip)
4) Flash via Odin
5) Enter stock recovery and wipe data
I'm not too keen on showing the way because an official Android 10 update is around the corner (being intensively beta-tested in China), which could potentially fix the bunch of bugs in running GSIs (most critical being call audio).
AndyYan said:
So slightly more details:
1) Make sure Magisk is properly installed (patch AP) and running on your device first, likely because we need it to disable dm-verity
2) Download any ARM64 AB GSI and rename the image (*.img) to system.img.ext4
3) Pack it into tar format (e.g. 7-zip)
4) Flash via Odin
5) Enter stock recovery and wipe data
I'm not too keen on showing the way because an official Android 10 update is around the corner (being intensively beta-tested in China), which could potentially fix the bunch of bugs in running GSIs (most critical being call audio).
Click to expand...
Click to collapse
im noob bro can you give me your facebook or instagram please :<
@deadinside322 I see you're from 4PDA, greetings. The flashing process does not involve TWRP (we don't have one), which is admittedly unorthodox. What error did you encounter anyway?
BTW I've tried a few ways to port TWRP with no success. I wish you luck there, and don't forget to open-source if you do succeed.
tomznottomo said:
im noob bro can you give me your facebook or instagram please :<
Click to expand...
Click to collapse
Sorry, I'm not interested in step-by-step assistance. If you're new to this you ought to take some more time to research to prevent screwing up. I can help when you're in progress and hit actual problems.
AndyYan said:
@deadinside322 I see you're from 4PDA, greetings. The flashing process does not involve TWRP (we don't have one), which is admittedly unorthodox. What error did you encounter anyway?
BTW I've tried a few ways to port TWRP with no success. I wish you luck there, and don't forget to open-source if you do succeed.
Sorry, I'm not interested in step-by-step assistance. If you're new to this you ought to take some more time to research to prevent screwing up. I can help when you're in progress and hit actual problems.
Click to expand...
Click to collapse
Hello, I also tried to port TWRP three times already, it didn’t work out in any way.
The problem was that the firmware in Odin was infinitely loaded, and some simply did not want to boot.
Android 10 has released for both A60 (A6060ZCU1BTC9) and M40. I've switched to using it as base for GSIs, and it fixes the call speaker problem; other mentioned issues remain. The flashing process stays the same as well.
Changing firmware galaxy m40 to galaxy a60 open china
Hi, im using galaxy m40, if i flash the galaxy a60 firmware, my phone work or brick, has any one try that?
have anyone tried flasing android 12 gsi to m40?
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.
I have been trying to get a custom rom flashed on my Redmi 9T the past two days.
The problem I am facing is that the touch screen is not responsive with the flashed ROMs that I have tried.
ROMs I have tried:
PixelPlusUI_3.9_juice-11.0-20210912-1736-OFFICIAL
LegionOS-v3.13-juice-20210922-OFFICIAL-GAPPS
Arrow-v11.0-juice-COMMUNITY-20210809-GAPPS
crDroidAndroid-11.0-20210927-juice-v7.10
What did make the touch screen work was to flash "boot.img" from one of the android 11 builds of MIUI such as "xiaomi.eu_multi_HMNote94G_HM9T_POCOM3_21.9.8_v12-11" or "xiaomi.eu_multi_HMNote94G_HM9T_POCO_M3_21.5.27_v12-11" after flashing the custom ROM, but this resulted in "Sytem UI" crashing and wifi not working. There were probably other things that didn't work but I can't have a phone without WiFi so this was not a solution for me.
After looking into what "boot.img" contains, it seems like it contains the kernel and other important system related components.I then tried to flash the following kernels over a new install of the custom ROMs "crDroid" and "PixelPlusUI 3.9":
StormBreaker-lime-r3-0909-0545
CartelProject-lime-BETA-20210915-07
Optimus_Drunk_Citrus_v11.1
But they did not help with getting the touch screen to work.
I also tried a combination of a "boot.img" from an offical android 11 EU MIUI ROM and these three kernels in the hope that I would keep the touch screen fix from "boot.img" and get wifi from the kernels, however every time the kernel was flashed the touch screen stopped working.
This leads me to believe the kernel itself makes the touch screen not work, and other things from the "boot.img" make the WiFi stop working.
So I have a few questions I hope someone can answer:
When do you think Xiaomi will release the source-code for the android 11 kernels that they use in their new MIUI ROMs? As I don't know their release cycles.
When will the firmware for the NVT-ts touchscreen version of Redmi 9T be added to custom kernels?
Is there a way for me to extract the Android 11 MIUI kernel from "boot.img" and flash ONLY that, if that fixes my touchscreen and does not break my WiFi? (If this is legal/allowed/possible)
I don't know anything about android development so if I am wrong please correct me.
Thank you in advance.
1.Download an official firmware, boot your device into your Fastboot Mode with Power+Volume Down Button connect your device to your pc and launch the flash_all.bat
When the flash is completed go to the Stock Recovery with Power Button+Volume Up Button, clean the data and wait your device to boot. When your device booted setting it up and enable USB Debugging from the Developer Tools.
2. Now boot your device to Fastboot Mode using Power Button+Volume Down and try to Flash TWRP or OrangeFOX.
3. Boot your device into Recovery using Power Button+Volume Up
4. Now make a CLEAN FLASH:
Format Data
Flash latest MIUI Weekly
Flash ROM zip
Flash Gapps (for Vanilla build)
Format Data
Reboot System,
Enjoy!
MIUI Weekly Firmware (Lime):Download
Fastboot Firmware tgz:Download
Atanassoww said:
1.Download an official firmware, boot your device into your Fastboot Mode with Power+Volume Down Button connect your device to your pc and launch the flash_all.bat
When the flash is completed go to the Stock Recovery with Power Button+Volume Up Button, clean the data and wait your device to boot. When your device booted setting it up and enable USB Debugging from the Developer Tools.
2. Now boot your device to Fastboot Mode using Power Button+Volume Down and try to Flash TWRP or OrangeFOX.
3. Boot your device into Recovery using Power Button+Volume Up
4. Now make a CLEAN FLASH:
Format Data
Flash latest MIUI Weekly
Flash ROM zip
Flash Gapps (for Vanilla build)
Format Data
Reboot System,
Enjoy!
MIUI Weekly Firmware (Lime):Download
Fastboot Firmware tgz:Download
Click to expand...
Click to collapse
Thank you for the reply.
However I believe that this is what I did do when I set up the phone with the ROMs.
I still tried to do it exactly as you explained, however this did not work.
I got into a bootloop after flashing firmware through fastboot, even if I cleaned the data using recovery. I tried the Recovery version of the firmware and this worked fine so after that I followed your tutorial just as you described.
This still didn't work, when booted into the Custom ROM the touch screen was still not working at all.
In the meanwhile I found this blog-post:
lemon – Encik Kunci
Posts about lemon written by Encik Kunci
encikkunci.wordpress.com
Where he states and I quote: "Phones with nt36672d display isn’t supported yet." this was posted August 11, 2021.
I don't know who he is or how he knows that.
I am pretty sure it's a kernel problem or firmware or something, regarding the screen being NVT-ts and probably the "nt36672d" variant.
This makes me very sad.
Its indeed an kernel issue, there's ( at least) two screen revisions from two different vendors
coffeemakerexpress said:
Thank you for the reply.
However I believe that this is what I did do when I set up the phone with the ROMs.
I still tried to do it exactly as you explained, however this did not work.
I got into a bootloop after flashing firmware through fastboot, even if I cleaned the data using recovery. I tried the Recovery version of the firmware and this worked fine so after that I followed your tutorial just as you described.
This still didn't work, when booted into the Custom ROM the touch screen was still not working at all.
In the meanwhile I found this blog-post:
lemon – Encik Kunci
Posts about lemon written by Encik Kunci
encikkunci.wordpress.com
Where he states and I quote: "Phones with nt36672d display isn’t supported yet." this was posted August 11, 2021.
I don't know who he is or how he knows that.
I am pretty sure it's a kernel problem or firmware or something, regarding the screen being NVT-ts and probably the "nt36672d" variant.
This makes me very sad.
Click to expand...
Click to collapse
I found this in 4pda:
Quote a reply: Yes, I had the same thing. By the way, if we are talking about OrangeFox recovery, which did not start at all, then it was necessary to use a newer version, I found a link to a google drive on the xda forum, it did not start there.
And on the touch, I also tried 2 custom firmware on them, everything started, but the touch did not work in principle. Only on off or lightweight everyone and on xiaomi.eu worked. I suppose the same case, but I can refine it when the phone is sent back.
ps: Due to freezes and rebots - in the service they changed the motherboard in the end, I'm waiting for the parcel now.
superdragonpt said:
Its indeed an kernel issue, there's ( at least) two screen revisions from two different vendors
Click to expand...
Click to collapse
I see, so my assumption was correct. Thank you for clarifying.
Do you know how often Xiaomi (or if they will at all) release firmware/kernel source codes, and do you know if custom kernel makers/Custom ROM makers, will actually update their kernels/ROMs to use this in the future?
And is there a way/place for me to keep updated on if Xiaomi releases the needed firmware/sourcecode for this display, so that I can ask ROM makers/Kernel makers nicely to add the firmware, assuming they don't know about this issue?
Atanassoww said:
I found this in 4pda:
Quote a reply: Yes, I had the same thing. By the way, if we are talking about OrangeFox recovery, which did not start at all, then it was necessary to use a newer version, I found a link to a google drive on the xda forum, it did not start there.
And on the touch, I also tried 2 custom firmware on them, everything started, but the touch did not work in principle. Only on off or lightweight everyone and on xiaomi.eu worked. I suppose the same case, but I can refine it when the phone is sent back.
ps: Due to freezes and rebots - in the service they changed the motherboard in the end, I'm waiting for the parcel now.
Click to expand...
Click to collapse
So you have the same problem? I'm not sure I understand what you mean here, aside from the touchscreen not working for you either due to this weird display model.
coffeemakerexpress said:
I see, so my assumption was correct. Thank you for clarifying.
Do you know how often Xiaomi (or if they will at all) release firmware/kernel source codes, and do you know if custom kernel makers/Custom ROM makers, will actually update their kernels/ROMs to use this in the future?
And is there a way/place for me to keep updated on if Xiaomi releases the needed firmware/sourcecode for this display, so that I can ask ROM makers/Kernel makers nicely to add the firmware, assuming they don't know about this issue?
So you have the same problem? I'm not sure I understand what you mean here, aside from the touchscreen not working for you either due to this weird display model.
Click to expand...
Click to collapse
Yes or is not Supported right now..
This is just a small update with a possible fix that I haven't tried yet because I'm tired of flashing ROMs all day, I will try it later if I get the motivation to do so. I post this because someone else might have the energy to test this themselves. If I test this I will update this post with an edit or bump this thread.
I Found on a forum called 4PDA where a user by the name "Void_dp" talks about a Xiaomi Redmi 9T with a nt36672d display. The forum is in Russian, but use a translator if you are interested. It is the post this url links to:
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки - 4PDA
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки
4pda.to
I do not know if the website itself or this user is trustworthy or correct, so try this with caution and I am not responsible for anything you decide to do or happens to you or your computer, or phone.
In short he explains that crDroid 7.9 (7.10 is the current version, and is the one I tried) use a different kernel than the Stormbreaker kernel than crDroid 7.10 uses.
He says if you have crDroid 7.10 installed you have to format data before trying this.
1. Download crDroid 7.9 and crDroid 7.10
2. Get the "boot.img" from the crDroid 7.9 rom and extract it
3. Open the zip file for crDroid 7.10 (do not extract anything) and replace the "boot.img" (7.10 version) with the one you just extracted (7.9 version)
4. Do a clean flash with this modified ROM you just made.
That is all he said, but if it doesn't work my first thought is to try the original crDroid 7.9 rom, if you don't care about running the latest update. This is probably not smart in relation to security patches and stuff like that. I take no responsibility for whatever happens.
Additional information:
I checked the Changelog for the crDroid roms, and they changed the kernel from "Optimus Drunk kernel 11.0" to "Stormbreaker" when they upgraded their ROMs version from 7.9 to 7.10.
I tried using the "Optimus Drunk kernel 11.1" kernel in my trial and error with the ROMs without luck, so I will try to flash some roms together with the "Optimus Drunk kernel 11.0" if I can find it.
Link to crDroid ROM for Redmi 9t:
crDroid.net - Download crDroid for supported devices
official crDroid ROM website
crdroid.net
coffeemakerexpress said:
This is just a small update with a possible fix that I haven't tried yet because I'm tired of flashing ROMs all day, I will try it later if I get the motivation to do so. I post this because someone else might have the energy to test this themselves. If I test this I will update this post with an edit or bump this thread.
I Found on a forum called 4PDA where a user by the name "Void_dp" talks about a Xiaomi Redmi 9T with a nt36672d display. The forum is in Russian, but use a translator if you are interested. It is the post this url links to:
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки - 4PDA
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки
4pda.to
I do not know if the website itself or this user is trustworthy or correct, so try this with caution and I am not responsible for anything you decide to do or happens to you or your computer, or phone.
In short he explains that crDroid 7.9 (7.10 is the current version, and is the one I tried) use a different kernel than the Stormbreaker kernel than crDroid 7.10 uses.
He says if you have crDroid 7.10 installed you have to format data before trying this.
1. Download crDroid 7.9 and crDroid 7.10
2. Get the "boot.img" from the crDroid 7.9 rom and extract it
3. Open the zip file for crDroid 7.10 (do not extract anything) and replace the "boot.img" (7.10 version) with the one you just extracted (7.9 version)
4. Do a clean flash with this modified ROM you just made.
That is all he said, but if it doesn't work my first thought is to try the original crDroid 7.9 rom, if you don't care about running the latest update. This is probably not smart in relation to security patches and stuff like that. I take no responsibility for whatever happens.
Additional information:
I checked the Changelog for the crDroid roms, and they changed the kernel from "Optimus Drunk kernel 11.0" to "Stormbreaker" when they upgraded their ROMs version from 7.9 to 7.10.
I tried using the "Optimus Drunk kernel 11.1" kernel in my trial and error with the ROMs without luck, so I will try to flash some roms together with the "Optimus Drunk kernel 11.0" if I can find it.
Link to crDroid ROM for Redmi 9t:
crDroid.net - Download crDroid for supported devices
official crDroid ROM website
crdroid.net
Click to expand...
Click to collapse
I DIDN't work for me, I got a bootloop, maybe it will work for u
hamid_dabouz said:
I DIDN't work for me, I got a bootloop, maybe it will work for u
Click to expand...
Click to collapse
Thats sad to hear, this phone is a nightmare. I haven't tried this yet, maybe I will try this weekend.
I'm wondering though, did you FORMAT data after flashing?
By bootloop, which of these do you mean:
That it never enters the "loading phase" of the OS (Android/rom splash screen)
That it gets stuck and restarts in the "loading phase" of the OS (Android/rom splash screen)
That it just kicks you to recovery/fastboot over and over again, without showing the OS loading screen
Or something else?
coffeemakerexpress said:
Thats sad to hear, this phone is a nightmare. I haven't tried this yet, maybe I will try this weekend.
I'm wondering though, did you FORMAT data after flashing?
By bootloop, which of these do you mean:
That it never enters the "loading phase" of the OS (Android/rom splash screen)
That it gets stuck and restarts in the "loading phase" of the OS (Android/rom splash screen)
That it just kicks you to recovery/fastboot over and over again, without showing the OS loading screen
Or something else?
Click to expand...
Click to collapse
Ohh Jeesus...
OK I just got my t9, and started the BL unlock, unfortunately I still need to wait ~ 1 week.
So I can't do testing at the moment
My unit has this very same touch screen, so seems I will likely have this same issue in the future.
I took a look at the kernel source provided by Xiaomi ( android 10 only)
And this touch variant isn't there in the defconfig
since the same kernel is used by 4 devices ( including t9, poco m3,etc )
I took the opportunity to check the few custom kernels that already exist for poco M3, and you guys should definitely try the poco m3 " stormbreaker" kernel, since it includes more TP drivers and the correct loading of both Novatek's TP drivers firmware
Cheers
superdragonpt said:
OK I just got my t9, and started the BL unlock, unfortunately I still need to wait ~ 1 week.
So I can't do testing at the moment
My unit has this very same touch screen, so seems I will likely have this same issue in the future.
I took a look at the kernel source provided by Xiaomi ( android 10 only)
And this touch variant isn't there in the defconfig
since the same kernel is used by 4 devices ( including t9, poco m3,etc )
I took the opportunity to check the few custom kernels that already exist for poco M3, and you guys should definitely try the poco m3 " stormbreaker" kernel, since it includes more TP drivers and the correct loading of both Novatek's TP drivers firmware
Cheers
Click to expand...
Click to collapse
Thank you for respond, But i already flashed Two versions of " stormbreaker"kernel one of them worked but the touch is going insane, if you clicked on somewhere on the screen it will respond in other place of the screen ( i hope you understand what i'm saying)
hamid_dabouz said:
Thank you for respond, But i already flashed Two versions of " stormbreaker"kernel one of them worked but the touch is going insane, if you clicked on somewhere on the screen it will respond in other place of the screen ( i hope you understand what i'm saying)
Click to expand...
Click to collapse
Oh i see...
Well since the weekly MIUI EU a11 ROMs seems to work alright ( as per the users feedback) , perhaps this can be easily fixed.
Just a matter of extracting from those android 11 kernel the DTB, and convert dtb to dts and the touch firmware loading binary and fix the kernel entries.
Assuming that the tp driver is the same or similar, and the issue is just the firmware blob and DTS
Let's see
Cheers
Atanassoww said:
Ohh Jeesus...
Click to expand...
Click to collapse
Why that reaction? I am here to learn and try to solve my problem, if you have any advice please elaborate on why what I said was wrong or dumb so I won't make the same mistake again.
superdragonpt said:
OK I just got my t9, and started the BL unlock, unfortunately I still need to wait ~ 1 week.
So I can't do testing at the moment
My unit has this very same touch screen, so seems I will likely have this same issue in the future.
I took a look at the kernel source provided by Xiaomi ( android 10 only)
And this touch variant isn't there in the defconfig
since the same kernel is used by 4 devices ( including t9, poco m3,etc )
I took the opportunity to check the few custom kernels that already exist for poco M3, and you guys should definitely try the poco m3 " stormbreaker" kernel, since it includes more TP drivers and the correct loading of both Novatek's TP drivers firmware
Cheers
Click to expand...
Click to collapse
I will maybe try the Stormbreaker kernel for Poco M3 this weekend as well then to check it out.
superdragonpt said:
Oh i see...
Well since the weekly MIUI EU a11 ROMs seems to work alright ( as per the users feedback) , perhaps this can be easily fixed.
Just a matter of extracting from those android 11 kernel the DTB, and convert dtb to dts and the touch firmware loading binary and fix the kernel entries.
Assuming that the tp driver is the same or similar, and the issue is just the firmware blob and DTS
Let's see
Cheers
Click to expand...
Click to collapse
Thank you for this informative answer, do I take it as this is something you will look into? If I can help by using adb or something, to get information from my phone just tell me what to do.
superdragonpt said:
Oh i see...
Well since the weekly MIUI EU a11 ROMs seems to work alright ( as per the users feedback) , perhaps this can be easily fixed.
Just a matter of extracting from those android 11 kernel the DTB, and convert dtb to dts and the touch firmware loading binary and fix the kernel entries.
Assuming that the tp driver is the same or similar, and the issue is just the firmware blob and DTS
Let's see
Cheers
Click to expand...
Click to collapse
Is this the extract you were talking about? It has the firmware for the touchscreens and everything for android 11. but it is for the Chinese version, so I don't know if that matters.
redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
qssi-user 11 RKQ1.201004.002 V12.0.3.0.RJQCNXM release-keys - redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
github.com
I don't know if this is relevant but I thought I would share it since I found it. Someone smarter than me can maybe use it to make the touchscreen work.
I fix dt2w on Xtended custom rom. Replace kernel and flash Magisk extension. I don.t try others roms....
coffeemakerexpress said:
Is this the extract you were talking about? It has the firmware for the touchscreens and everything for android 11. but it is for the Chinese version, so I don't know if that matters.
redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
qssi-user 11 RKQ1.201004.002 V12.0.3.0.RJQCNXM release-keys - redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
github.com
I don't know if this is relevant but I thought I would share it since I found it. Someone smarter than me can maybe use it to make the touchscreen work.
Click to expand...
Click to collapse
coffeemakerexpress said:
Hello.
I have been trying to get a custom rom flashed on my Redmi 9T the past two days.
The problem I am facing is that the touch screen is not responsive with the flashed ROMs that I have tried.
ROMs I have tried:
PixelPlusUI_3.9_juice-11.0-20210912-1736-OFFICIAL
LegionOS-v3.13-juice-20210922-OFFICIAL-GAPPS
Arrow-v11.0-juice-COMMUNITY-20210809-GAPPS
crDroidAndroid-11.0-20210927-juice-v7.10
What did make the touch screen work was to flash "boot.img" from one of the android 11 builds of MIUI such as "xiaomi.eu_multi_HMNote94G_HM9T_POCOM3_21.9.8_v12-11" or "xiaomi.eu_multi_HMNote94G_HM9T_POCO_M3_21.5.27_v12-11" after flashing the custom ROM, but this resulted in "Sytem UI" crashing and wifi not working. There were probably other things that didn't work but I can't have a phone without WiFi so this was not a solution for me.
After looking into what "boot.img" contains, it seems like it contains the kernel and other important system related components.I then tried to flash the following kernels over a new install of the custom ROMs "crDroid" and "PixelPlusUI 3.9":
StormBreaker-lime-r3-0909-0545
CartelProject-lime-BETA-20210915-07
Optimus_Drunk_Citrus_v11.1
But they did not help with getting the touch screen to work.
I also tried a combination of a "boot.img" from an offical android 11 EU MIUI ROM and these three kernels in the hope that I would keep the touch screen fix from "boot.img" and get wifi from the kernels, however every time the kernel was flashed the touch screen stopped working.
This leads me to believe the kernel itself makes the touch screen not work, and other things from the "boot.img" make the WiFi stop working.
So I have a few questions I hope someone can answer:
When do you think Xiaomi will release the source-code for the android 11 kernels that they use in their new MIUI ROMs? As I don't know their release cycles.
When will the firmware for the NVT-ts touchscreen version of Redmi 9T be added to custom kernels?
Is there a way for me to extract the Android 11 MIUI kernel from "boot.img" and flash ONLY that, if that fixes my touchscreen and does not break my WiFi? (If this is legal/allowed/possible)
I don't know anything about android development so if I am wrong please correct me.
Thank you in advance.
Click to expand...
Click to collapse
Atanassoww said:
1.Download an official firmware, boot your device into your Fastboot Mode with Power+Volume Down Button connect your device to your pc and launch the flash_all.bat
When the flash is completed go to the Stock Recovery with Power Button+Volume Up Button, clean the data and wait your device to boot. When your device booted setting it up and enable USB Debugging from the Developer Tools.
2. Now boot your device to Fastboot Mode using Power Button+Volume Down and try to Flash TWRP or OrangeFOX.
3. Boot your device into Recovery using Power Button+Volume Up
4. Now make a CLEAN FLASH:
Format Data
Flash latest MIUI Weekly
Flash ROM zip
Flash Gapps (for Vanilla build)
Format Data
Reboot System,
Enjoy!
MIUI Weekly Firmware (Lime):Download
Fastboot Firmware tgz:Downl
Click to expand...
Click to collapse
bogteo said:
I fix dt2w on Xtended custom rom. Replace kernel and flash Magisk extension. I don.t try others roms....
Click to expand...
Click to collapse
Please can you explain more ?
I tried with crdroid 7.9 without success. still cannot use the touchscreen
m210j19sy I began with global miui rom
I was following the guide from https://topjohnwu.github.io/Magisk/install.html.
When I run the command
Code:
fastboot flash boot /path/to/magisk_patched.img
I get the following error :
Code:
>fastboot flash boot ./magisk_patched-24300_WbyGV.img
Sending 'boot_a' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Note that I had already waited 7 days and unlocked the device successfully with https://en.miui.com/unlock/download_en.html so I am not sure why the error is showing that my device is locked.
The Mi unlock tool said that my device was successfully unlocked.
Update : Never mind, I resolved it.
DEAR PEOPLE FROM THE FUTURE: Here's what we've figured out so far:
When you reboot into using `adb reboot fastboot` command we will land in fastbootd mode instead of fastboot mode. Turning off the mobile and using down arrow and power button together is the ideal way to reach the fastboot mode.
Magisk throws the above error when running in fastbootd mode, but the same command works great when running in fastboot mode.
So quick guide for rooting Xiaomi 12 Pro and passing Safetynet is to
1) unlock the device by using MIUI Unlock (It may take 7 days)
2) Follow the topjohnwu's guide to root your phone.
3) Enable zygisk and deny list in Magisk.
4) Apply the Universal Safetynet Fix module in Magisk
12 Pro doesnt have A / B partition as 12?
[ROOT]ing Xiaomi 12 with Magisk
Sources used: https://www.getdroidtips.com/root-xiaomi-12-and-12-pro/ 1. First unlock your bootloader. This thread does not cover this. I suggest you do not try to tamper with the 1week~ time gate you will encounter else it may get longer should...
forum.xda-developers.com
seems it went well
Code:
fastboot flash boot MI12pro_magisk_patched-24300_xl4XD.img
Sending 'boot_a' (196608 KB) OKAY [ 4.672s]
Writing 'boot_a' OKAY [ 0.381s]
Finished. Total time: 5.861s
Anyway , how to find out if device has A/B partition?
killeriq said:
seems it went well
Code:
fastboot flash boot MI12pro_magisk_patched-24300_xl4XD.img
Sending 'boot_a' (196608 KB) OKAY [ 4.672s]
Writing 'boot_a' OKAY [ 0.381s]
Finished. Total time: 5.861s
Anyway , how to find out if device has A/B partition?
Click to expand...
Click to collapse
You can see from the result "Sending 'boot_a'" that it has A/B partition. But as far as I know you don't have to flash in both the partitions. Just default flash boot command should be enough.
Good to know that it went well!
It is really complicated for a normal being to root this device, and I consider that I have a certain "skill" in this area. At the moment it is not possible to use Orange Fox, TWRP and even less to use Magisk in an uncomplicated way. Is there a specific reason?
what I did to root my Xiaomi 12 pro (using eu rom but the proceedure will be same for stock rom too)
DO AT YOUR OWN RISK
1. Unlock the device
2. get boot image of your current rom & latest magisk app from github
3. install magisk app & patch the boot image with magisk app
4. reboot bootloader => adb reboot bootloader which opens fastboot, do not use adb reboot fastboot which will open fastbootd
5. open terminal in your pc and using fastboot boot magisk_patched.img boot into magisk patched boot, then fastboot reboot
6. now you can use root till u reboot so open magisk app now and install magisk using direct install method which will patch stock boot image which is currently being used.
7. reboot device
8. (Optional)enable zygisk, denylist and configure deny list
9. (Optional)I install all the modules which I want to like lsposed, energized protection, sui etc.
10. (Optional) if you are facing issues with any banking or other apps which recognises root or lsposed use hidemyapplist xposed module, if still issue persist then disable denylist and flash Shamiko magisk module it won't work with denylist enabled.
Q. Won't it be sufficient if we flash boot image directly?
A. you can, but do flash both partitions xiaomi 12 pro, I personally faced an issue with this method once so I don't flash and instead use magisk app to patch.
Q. Do we need Safety net module?
A. In my use case no after enabling zygisk and configuring denylist u can basically stop apps from using root by denying their requests so safety net test will pass once you configure it in denylist remember to turn on google services and banking apps at least in denylist.
Q. My Banking app still recognize root, how to hide it?
A. If u have lsposed use HideMyAppList module and configure all the apps which are to be not allowed to use root, if it still doesn't work then use Shamiko module with hide my app list module, to use Shamiko you have to disable denylist.
Q. Can I unroot?
A. Yes you can just flash original boot or use uninstall option in magisk app or update your rom, there are many ways to remove root access.
Q. Are all apps working?
A. yes I am from india, here all banking/Wallets/UPI apps are working after configuring denylist and hidemyapplist module, As of now I am not using Shamiko
Same here, I rooted my 12 Pro and its working great.
What I did first I flashed the xiaomi EU stable Rom first, then extracted boot file, patched and flashed via fastboot. No need for TWRP at all and I wont bother installing it either. Fastboot application is straight forward and smooth
Hi i have a question by Miunlocker is written that i cant use fingerprint unlocking after Bootloader Unlocking. is that true? Or can i activate that later again with MagiskHide Props config, safety netfix and so on? or is that forever not possible with unlock and root? Cause then i think about getting an other Phone. Regards and thanks
raymann89 said:
Hi i have a question by Miunlocker is written that i cant use fingerprint unlocking after Bootloader Unlocking. is that true? Or can i activate that later again with MagiskHide Props config, safety netfix and so on? or is that forever not possible with unlock and root? Cause then i think about getting an other Phone. Regards and thanks
Click to expand...
Click to collapse
Their warnings are very misleading. Everything works as it should, except Mi device location, but you have Google device location for that purpose. My phone is unlocked and rooted, so I'm speaking from experience. SafetyNet passes, bank apps work, PayPal works, etc...
yes that that whole thing work i know, i have at the monent an oneplus 10 pro rooted, but i was worried cause there statments thats why i asked, but good to know that everything works with magisk, thank you Yes i mean the device location dont interest me persoanlly
Hi i have a few Questions, my Unlock Waiting Time is Today over, and i wanted to ask first - is it better to use the XiaomiEU Roms rather then the Global Version? Then after that, by my Oneplus before i just Unlocked, rooted with magisk as Patch File from Payloader and enabled then the hide list and the other Settings with Fingerprint. Now for the Xiaomi is TWRP Available so better use that ? and With Xiaomi EU Rom, TWRP and Magisk Hidemyapps and Safetynetfix iam able to use Banking Apps and Gpay ? thanks and sorry for the many Questons
raymann89 said:
Hi i have a few Questions, my Unlock Waiting Time is Today over, and i wanted to ask first - is it better to use the XiaomiEU Roms rather then the Global Version? Then after that, by my Oneplus before i just Unlocked, rooted with magisk as Patch File from Payloader and enabled then the hide list and the other Settings with Fingerprint. Now for the Xiaomi is TWRP Available so better use that ? and With Xiaomi EU Rom, TWRP and Magisk Hidemyapps and Safetynetfix iam able to use Banking Apps and Gpay ? thanks and sorry for the many Questons
Click to expand...
Click to collapse
Xiaomi Eu roms are better than stock and
no need to root, the play store is certified.
Okay thanks, so i take the XiaomiEU Rom. No i want to Root cause i cant acess Android/data without root and thats annoying for me in some games and apps that the XiaomiEU Rom has an Safetynet inside i read yes.
Whether the Xiaomi.EU roms are better than stock is highly subjective. They may be better than the stock chinese rom for international use, but others have reported that the EEA and Global ROMs are working perfectly, the EEA adheres to the necessary privacy and advertising laws and they are developed & distributed by Xiaomi officially.
Additionally xiaomi.eu roms are not official in any way, are not open source, and are "modified" by a group of unknown people who take no responsibility for their version whatsoever, so there is definitely a trust aspect you need to be aware of and if you ever have any problems it is just too bad.
murakh said:
Whether the Xiaomi.EU roms are better than stock is highly subjective. They may be better than the stock chinese rom for international use, but others have reported that the EEA and Global ROMs are working perfectly, the EEA adheres to the necessary privacy and advertising laws and they are developed & distributed by Xiaomi officially.
Additionally xiaomi.eu roms are not official in any way, are not open source, and are "modified" by a group of unknown people who take no responsibility for their version whatsoever, so there is definitely a trust aspect you need to be aware of and if you ever have any problems it is just too bad.
Click to expand...
Click to collapse
11 years that they provide roms, do you really believe that they are unknown, present on XDA on multiple devices.
Their roms have been taken over by MUIMIX, ONE os, Mi rom etc, without bringing anything more apart from a few additional options for some and for others nothing and having tried them all on different devices I always came back to the Xiaomi EU.
Ads and restrictions of EEA or Global roms no thanks.
What is interesting is to keep the bootloader unlocked because in the event of a problem, recovery will be possible and relatively simple, which will not be the case on a stock ROM with the bootloader locked.
Xiaomi sends updates on a stable rom but the update is a stable beta, many have had their phones blocked because of this with phones no longer guaranteed.
When a build has a problem, it is reuploaded the same day, which is really not the case with official Xiaomi.
Try to do better.
Spoiler: Xiaomi EU rom
Based on China Stable / Weekly builds
3way reboot menu (in dev settings)
MIUI Contacts and Dialer
Removed ads in MIUI system apps
MIUI Dialer and Messages apps
Steps counter in Assistant screen
More shortcuts on left lockscreen
Wake up gestures for all devices
AI preloading option in MIUI Lab for all devices
Option to auto-expand first notification
Notifications priority settings
More edit options in Gallery app
Enabled MiDrive in File Explorer
Added landscape mode for SMS app
Sunrise/Sunset in the weather app
Google apps support integrated
Removed 5GHz region restrictions
Confirm dials from call logs
Morning report on alarm at morning
More apps supported for AOD notifications
More styles for AOD screen
Raise to wake gesture
AOD notification received animation
Tap fingerprint sensor to wake toggle
More Camera features
Double tap to lock screen
Battery AI scenes
Allowed disabling specific system apps
Importing theme .mtz from zhuti.xiaomi.com via ThemeManager
No useless Chinese bloatware apps
More free RAM due to less background processes
Mi Video, Mi Music, Mi Browser: No any useless Chinese content
No possibility to re-lock bootloader accidentally with flash any xiaomi.eu release
Added real 27 languages translation made by Official MIUI Fansites and MIUI Fans
Added EU T9 dialer support
Added charging sound switch
Optimized GPS settings for EU
Optimized Battery consumption
Optimized RAM consumption
Added GSMalphabet into SMS app options
SafetyNet passed by default (Google Pay)
Play Store Certified
Deodexed
Added automated tasks in Security app
Added game speed booster
Widevine L1 (for supported devices)
NOSS8 said:
11 years that they provide roms, do you really believe that they are unknown, present on XDA on multiple devices.
Click to expand...
Click to collapse
Not officially on XDA, only as an installation guide since their ROMs do not meed the requirements.
NOSS8 said:
Their roms have been taken over by MUIMIX, ONE os, Mi rom etc, without bringing anything more apart from a few additional options for some and for others nothing and having tried them all on different devices I always came back to the Xiaomi EU.
Click to expand...
Click to collapse
Subjective preference. Subjective, as I indicated.
NOSS8 said:
Ads and restrictions of EEA or Global roms no thanks.
Click to expand...
Click to collapse
Subjective preference again.
NOSS8 said:
Try to do better.
Click to expand...
Click to collapse
Nowhere did I insult you, and this insult is unnecessary. My response was to the original question of whether xiaomi.eu was better or not. My response was less subjective and highlighted multiple other user's experiences of global & EEA (although even Chinese ROM with google services activated gets a lot of praise thesedays and that is what I use, but again that is my subjective preference which I am not trying to get anyone else to follow and did not even mention it).
Not that there is anything wrong with a subjective answer, yet to make a better informed choice either multiple subjective inputs are needed, or a non-subjective comparison.