[ROM/Kernel] Stock 7.1.1 B02 based for A2017G. The "We can do it better than zte" ed.
No fancy super nice pictures and no other great blabla here.
Thx @wineds for providing a TWRP backup from the system. It's the base of this.
Thx @SuperR. for his great kitchen.
Little mods:
init.d enabled
dm-verity disabled
SuperSU included
Spyware stuff:
tencentNLP removed
Email_ZTE removed
no further actions done on this.
For me it's working with the Universal Bootstack. You will find it in the LOS thread.
Flash it with TWRP.
Download:
The ROM --> https://www.androidfilehost.com/?fid=673368273298948672
The Stock Kernel if you played to much with the others -->https://www.androidfilehost.com/?fid=817550096634763383
p.s.: I've read about problem with big sdcards in conjunction with the original B02 rom. I've never been on this crap version, so I can't tell if there's a difference in the behaviour. But up to now I have no problem with my 128GB sandisk card. And yes, it's formated with extfs.
This rom can flash from twrp? What version of twrp?
Thank you, I was expecting something like this.
I use google translate
Enviado desde mi ZTE A2017U mediante Tapatalk
davidroid1 said:
This rom can flash from twrp? What version of twrp?
Thank you, I was expecting something like this.
I use google translate
Enviado desde mi ZTE A2017U mediante Tapatalk
Click to expand...
Click to collapse
For me TWRP 3.1 did its job.
tron1 said:
No fancy super nice pictures and no other great blabla here.
Thx @wineds for providing a TWRP backup from the system. It's the base of this.
Thx @SuperR. for his great kitchen.
Little mods:
init.d enabled
dm-verity disabled
SuperSU included
Spyware stuff:
tencentNLP removed
Email_ZTE removed
no further actions done on this.
For me it's working with the Universal Bootloader. You will find it in the LOS thread.
Flash it with TWRP.
Download:
The ROM --> https://www.androidfilehost.com/?fid=673368273298948672
The Stock Kernel if you played to much with the others -->https://www.androidfilehost.com/?fid=817550096634763383
p.s.: I've read about problem with big sdcards in conjunction with the original B02 rom. I've never been on this crap version, so I can't tell if there's a difference in the behaviour. But up to now I have no problem with my 128GB sandisk card. And yes, it's formated with extfs.
Click to expand...
Click to collapse
How did you disable dm-verity? Patch the boot image with the no-verity zip from nethunter?
With the removal of TNL does the Google Location Provider now provide the location information?
sToRm1nG said:
How did you disable dm-verity? Patch the boot image with the no-verity zip from nethunter?
With the removal of TNL does the Google Location Provider now provide the location information?
Click to expand...
Click to collapse
Google maps showed me my correct location while beeing inside my house. So i guess it is working right. If not we still have the option to flash/install opengapps to make it run as designed.
tron1 said:
Google maps showed me my correct location while beeing inside my house. So i guess it is working right. If not we still have the option to flash/install opengapps to make it run as designed.
Click to expand...
Click to collapse
Thanks, I will probably try it myself since I am not completely satisfied with LOS.
What about dm-verity? Did you patch the boot image with the zip file I was talking about? I'm asking because I'd probably do it myself.
sToRm1nG said:
Thanks, I will probably try it myself since I am not completely satisfied with LOS.
What about dm-verity? Did you patch the boot image with the zip file I was talking about? I'm asking because I'd probably do it myself.
Click to expand...
Click to collapse
It's just a "click" in the SuperRs kitchen boot image config menu.
Anyone who has U model tried?
WesTD said:
Anyone who has U model tried?
Click to expand...
Click to collapse
I'm not sure if the U model contains the Tencent Network Location app (AFAIK it is not).
Pin Input necessary after installation ....
I´m have a A2017G with Stockrom B08 on MM and TWRP 3.1.0.0
Installed the first the Kernel and then the Nougat_7_1_1_B02_we_can_do_it_better_than_zte.zip.
Wipe Cache and Reboot to recovery , than into to the system.
Result:
Need a Pin for the first start, but no ok. I could input all numbers and delete it. But nothing go on.
Any Idea for my failure ?
Snoopy2006 said:
I´m have a A2017G with Stockrom B08 on MM and TWRP 3.1.0.0
Installed the first the Kernel and then the Nougat_7_1_1_B02_we_can_do_it_better_than_zte.zip.
Wipe Cache and Reboot to recovery , than into to the system.
Result:
Need a Pin for the first start, but no ok. I could input all numbers and delete it. But nothing go on.
Any Idea for my failure ?
Click to expand...
Click to collapse
Yes, I have an idea. You didn't read and/or under-stand what you have to flash and what not. You don't have to flash the kernel (it's just in case you played with other kernels, so you don't need to flash the whole system). The thing you have to flash before is the universal Bootstack from the LOS thread. For removing the pin do the following in TWRP:
head to Advanced > File Manager, and go to the /data/system folder. Scroll down and find the two files with the .key extension. Delete both of them (by tapping on the file and then tapping the “Delete” button). Then, delete all the files containing the word locksettings.
From MM B08 to Nougat 7.1.1 B02
tron1 said:
Yes, I have an idea. You didn't read and/or under-stand what you have to flash and what not. You don't have to flash the kernel (it's just in case you played with other kernels, so you don't need to flash the whole system). The thing you have to flash before is the universal Bootstack from the LOS thread. For removing the pin do the following in TWRP:
head to Advanced > File Manager, and go to the /data/system folder. Scroll down and find the two files with
Click to expand...
Click to collapse
At the Moment I`m back to MM B08 on the Axon 7 2017 G !
What should I flash ?
tron1 said:
Yes, I have an idea. You didn't read and/or under-stand what you have to flash and what not. You don't have to flash the kernel (it's just in case you played with other kernels, so you don't need to flash the whole system). The thing you have to flash before is the universal Bootstack from the LOS thread. For removing the pin do the following in TWRP:
head to Advanced > File Manager, and go to the /data/system folder. Scroll down and find the two files with the .key extension. Delete both of them (by tapping on the file and then tapping the “Delete” button). Then, delete all the files containing the word locksettings.
Click to expand...
Click to collapse
In my Systemfolder I find gatekeeper.password.key and gatekeeper.pattern.key. Should I remove these 2 Files ?
hi
thx for the build, but seems I missed something, because the gps is not working without wifi(gps cant lock on).
I tried google and here. coming from NucleaRom flashed only the rom and the universal bootstack.
can we select the apps which we want and which we do not want while installing ?
sendem said:
hi
thx for the build, but seems I missed something, because the gps is not working without wifi(gps cant lock on).
I tried google and here. coming from NucleaRom flashed only the rom and the universal bootstack.
Click to expand...
Click to collapse
Tried it with Sigic and GPS test tool, no problem here
I flashed the kernel now the gps its ok(so no problems for me) .dont use the latest twrp 3.1 it has some bugs.
best regards.
I understand you kept this close to stock, but I have 3 questions.
Does it support Live Wallpaper? (stock B02 doesn't)
Can you turn off the lock screen 'None'?
Does it run Daydream smoothly?
You need to put it in the viewer to really tell. I tried on other ROMS, but it was super choppy and jittery to the point of nausea.
Very good battery life, but no MTP connection possible. It's the same fault as with all LOS based roms (based on 7.1.2).
HuKu52 said:
Very good battery life, but no MTP connection possible. It's the same fault as with all LOS based roms (based on 7.1.2).
Click to expand...
Click to collapse
No problem here. Check bootstack/modem
Related
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases.
All information, including troubleshoot guides and notes, are in the Announcement Thread
Oh wowww. Thanks!!
Error in the thread title: 2015.8.4
Yay it's finally here!
I'm already using it and I must say it works fine
Man, this "universal MultiROM support" left me full of hope. I hope it works out. And it was time for a mods manager on Android, thanks topjohnwu
Working great on my N6!
topjohnwu has my vote for President!
(and a well deserved donation)
AMAZING!, now to be sure, if i have a rom and want to integrate Magisk, the correct order of flashing is:
1-rom
2-magisk
3-modded su (magisk compatible)
it's that the way?
topjohnwu said:
....Magisk Is A Magic Mask to Alter System Systemless-ly.
If you are running custom roms, dirty flash the rom again to remove all possible issues. If the rom includes SuperSU, unzip the boot image from the rom zip, and flash it through TWRP, flashify, fastboot etc. to restore to stock ramdisk......
....... you can now download Magisk and flash to your device.
To remove Magisk, restore your boot image back (Magisk will backup your boot image automatically in /data/stock_boot(md5).img.gz), then delete /data/magisk.img.
Click to expand...
Click to collapse
is the following still applicable in the case of custom roms?
smohanv said:
1. Boot in to TWRP
2. go to Advanced / File Manager and delete folder named supersu
3. go to Advanced / Terminal and enter these two commandsecho SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersuThe first one forces systemless, the second prevents /su/xbin_bind from existing.4. Flashed Beta SuperSu 2.74-2 (we can notice while flashing this zip after the above script, we will not see the line saying "Disabling OTA". Also, end of flashing it warns that it takes longer time to boot.
5. Reboot device and enjoy systemless
6. To check if we have achieved systemless root, go to system/xbin folder and we should not see the file named "su".
7. I rebooted in to TWRP and flashed xposed 85.1 (also updated with 85.2 later) and installed the apk (Material design apk from this thread)
8. All done and my xposed works.....
Click to expand...
Click to collapse
Awesome....
Sent from my AO5510 using Tapatalk
Stuck at boot screen on the S7 Exynos variant, is this just for stock Android or did i do something wrong? I flashed the Magisk v1 then the phh root zip now im stuck at the boot screen ?
So wait, before i get excited this means things like viper4android can be installed without messing with system?
swipp3r said:
Stuck at boot screen on the S7 Exynos variant, is this just for stock Android or did i do something wrong? I flashed the Magisk v1 then the phh root zip now im stuck at the boot screen ?
Click to expand...
Click to collapse
Sure you probably did something wrong.
For starters you gave way to little information.
Did you follow the procedure from the OP exactly ?
What rom do you have, custom recovery if any, custom kernel if any ?
How did you flash ?
Come on people give this information by yourself please, don't let us pull it out of you everytime.
You know you are the one needing help than please try to give detailed information about your problem.
Sent from my Nexus 5 using XDA-Developers mobile app
grep_i said:
Sure you probably did something wrong.
For starters you gave way to little information.
Did you follow the procedure from the OP exactly ?
What rom do you have, custom recovery if any, custom kernel if any ?
How did you flash ?
Come on people give this information by yourself please, don't let us pull it out of you everytime.
You know you are the one needing help than please try to give detailed information about your problem.
Sent from my Nexus 5 using XDA-Developers mobile app
Click to expand...
Click to collapse
Stock marshmallow, flashed via twrp, and yes i followed the op correctly. No custom kernel.
swipp3r said:
Stuck at boot screen on the S7 Exynos variant, is this just for stock Android or did i do something wrong? I flashed the Magisk v1 then the phh root zip now im stuck at the boot screen ��
Click to expand...
Click to collapse
Did you flash phh's root zip from this thread's Downloads section or from original phh's thread? If the latter, then that's probably the culprit.
Nezorflame said:
[/COLOR]
Did you flash phh's root zip from this thread's Downloads section or from original phh's thread? If the latter, then that's probably the culprit.
Click to expand...
Click to collapse
The threads download section. Should i have downloaded from phhs thread?
swipp3r said:
The threads download section. Should i have downloaded from phhs thread?
Click to expand...
Click to collapse
Nah, you did right, I checked just in case, because thought of it myself. Need the developer's help then.
Nezorflame said:
Nah, you did right, I checked just in case, because thought of it myself. Need the developer's help then.
Click to expand...
Click to collapse
Thanks for trying bro.....
@topjohnwu this new "magisk" method. It doesn't allow Android Pay to work on custom roms like CyanogenMod does it? If I remove SU from CyanogenMod and use your root.
Magisk on (Yu Yureka) ARM64 device
i did a full clean wipe and then flashed rom, magisk and 'Magisk Compatible phh's SuperUser' - in that order. magisk manager app does not open.
Holy crap.. everything universal with support for extensions. This platform could be the beginning of a new era in mods. @topjohnwu amazing work. Don't want to be rude, but personally I think the name of the project is not as awesome as the project itself. "Magisk" sounds a bit cheesy.. :silly:
great work, will try it out soon! one little thing i noticed in the thread title...i guess it should be 2016
Thanks to "O grupo de discussões sobre tecnologia e outras coisas!...https://t.me/VegaData " for your solution.
Download GSI https://drive.google.com/file/d/1EnLAwEBaYLeepTSuQ2iUSoE8lm-csTPw/view?usp=sharing
(MIUI11-Aonly-9-VegaDataTests-exp-20191209-ErfanGSI.img.gz) ---extract before use
Information:
Android Version: 9
Brand: Xiaomi
Model: POCO F1
Codename: beryllium
Build Type: beryllium-user
Build Number: PKQ1.180729.001
Incremental: V11.0.5.0.PEJMIXM
Tags: release-keys
Security Patch: 2019-10-01
Fingerprint: Xiaomi/beryllium/beryllium:9/PKQ1.180729.001/V11.0.5.0.PEJMIXM:user/release-keys
Description: beryllium-user 9 PKQ1.180729.001 V11.0.5.0.PEJMIXM release-keys
Raw Image Size: 2.49 GiB
Clean Installation
Step:
1. flash latest Firmware https://mega.nz/#!QDplSYab!mrB5f8875VghQHfrrGvid4iJICMopkq3anZCipLWzqo
2. flash Vendor https://mega.nz/#!ECAG1aIS!OuGf9eVoiJpg0xreeLIarAWs5GkuCbu9AwR95MSlO-g
3. flash GSI as System Image
4. flash Permissiver v4.zip https://mega.nz/#!ETIwHQJC!Go5NfpgXFy5gPw8gFG8JbUCch7Eijw4rDp3NVTkhd-M
5. flash Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip https://mega.nz/#!gTohmQaR!ZL5jCeatYXUzUMx_moJseJ9o7b1RoLUf3o_PfOtn_aw
--Mount System & Vendor
6. flash Sound Fix (fixaudiogsi.zip) https://mega.nz/#!AD52wIhD!FM5GruKjw76gRnXqqLrh73CsSIZmldANlZrzyfVlcX0
7. flash DropVendorLightHAL.zip https://mega.nz/#!QKgVxaCI!lJuYDA2HjpP8msTbB7uXzW5jlvHImmHBtjjAdjt5R5g
8. flash DisableForceEncryption_Treble_v20.1.zip https://mega.nz/#!BHgRWYDS!jfuIRqTPTjS_lVy2tfpSbVRfqmxqqadeLFttgbKmhYQ
Reboot
-Verify your MI Account.
1.connect your WiFi 2. input you mi password. ...wait
- Magisk manager add MIUI_Auto_Brightness_Fix_v4_(pie).zip
https://mega.nz/#F!hT5UkSAQ!VCiS_BVC0Jlobpo6EMLsDg
-install GMS.apk and reboot
Coming soon --- Fingerprint Fix
Really great rom, everything works. Only missing feature is the face unlock. It's crazy smooth rom.
Hi, i plan to flash this one, is it better to use xiaomi flashtool or flashing them by hand?
ƁɐⱤᶒ said:
Hi, i plan to flash this one, is it better to use xiaomi flashtool or flashing them by hand?
Click to expand...
Click to collapse
By hand
zuhero said:
By hand
Click to expand...
Click to collapse
ok thanks
got it, but has problem with brightness,at most it remains low
Another noob question, is it better to be in china rom before going further with Miui 11 -Erfan GSIs or it is ok if i am on the EU Rom ?
and should i do a clean install before flashing anything?
pietroarnoldi said:
got it, but has problem with brightness,at most it remains low
Click to expand...
Click to collapse
I have no brightness problems
---------- Post added at 07:08 AM ---------- Previous post was at 07:06 AM ----------
ƁɐⱤᶒ said:
Another noob question, is it better to be in china rom before going further with Miui 11 -Erfan GSIs or it is ok if i am on the EU Rom ?
and should i do a clean install before flashing anything?
Click to expand...
Click to collapse
I don't think it matters cuz you're gonna flash the latest firmware.
Okay so after everything done, after reboot i 've been asked to unlock the device with the mi account, that succeed; except i have a message saying "An internal problem with your device has occurred. Please contact the manufacturer for more information."
On the latest Mega link i didn't find Magisk Manager.
And the external storage is working Yay!
ƁɐⱤᶒ said:
Okay so after everything done, after reboot i 've been asked to unlock the device with the mi account, that succeed; except i have a message saying "An internal problem with your device has occurred. Please contact the manufacturer for more information."
On the latest Mega link i didn't find Magisk Manager.
And the external storage is working Yay!
Click to expand...
Click to collapse
That message only appears one time after every boot, it doesn't matter, just ignore it. I'm using the latest magisk canary, working like a charm.
Understood, but i have another issue with Chrome that trying to update 299ko
i already checked authorizations under app settings
and made a video here
https://youtu.be/sp7jtkbLuKk
weird things is that i could install two apps without problems; any thought?
otherwise, this rom runs incredibly faster than the original one o_0'
Thanks for that!:good:
ƁɐⱤᶒ said:
Understood, but i have another issue with Chrome that trying to update 299ko
i already checked authorizations under app settings
and made a video here
https://drive.google.com/file/d/1BnNj6CH1tkQp1NQttDiBbTx6mORoRX9a/view?usp=sharing
weird things is that i could install two apps without problems; any thought?
otherwise, this rom runs incredibly faster than the original one o_0'
Thanks for that!:good:
Click to expand...
Click to collapse
Never had issues with chrome, try to reinstall app or clear data and cache from playstore and reboot.
Hi.
A video tutorial would be fine.
Thanks.
DANI36ZGZ said:
Hi.
A video tutorial would be fine.
Thanks.
Click to expand...
Click to collapse
i agree this installation is a bit more specific than what i already encounter, but following the steps on post is ok.
Many thanks for a great ROM and awesome work!!!
Please help about flash procedure:
3. flash GSI as System Image
Where is it please? And hot to flash it as system image?
Thanks!
Tom, thanks for everything you have done.
Only one question: when you fix fingerprint, will we have to flash whole system again or maybe only a part of it? Reading mode going to be fixed? (block blue light,useful to study)
thanks.
Edit:
@nirh216
Dude, in the bottom side, right side, there's a option to image file. click it, then choose the huge file (about 2gb) you donwloaded and flash it.
Edit2: Physical home button it's kinda useless to unlock right now, right? I cant see to use it even to unlock it, only as "home button". And i did not installed fix for auto brightness because mine is working, and i could not find how to install it by magisk, if anyone has atuto for it. thanks.
Edit3: 2 bugs I found. 1st Nav bar stop working after a while, needing to restart device to work. 2nd brightness from screen is definetly low, like half the bright from normal stock rom ----> I guess brightness is a problem from pocophone and about nav bar seems like tasker was fckng it up
Thanks.
Edit4: last edit lol. My twrp seems to be gone after doing every step and i cant find to install it again. you guys have twrp working?
tom.android said:
Thanks to "O grupo de discussões sobre tecnologia e outras coisas!...https://t.me/VegaData " for your solution.
Download GSI https://drive.google.com/file/d/1EnLAwEBaYLeepTSuQ2iUSoE8lm-csTPw/view?usp=sharing
(MIUI11-Aonly-9-VegaDataTests-exp-20191209-ErfanGSI.img.gz) ---extract before use
Information:
Android Version: 9
Brand: Xiaomi
Model: POCO F1
Codename: beryllium
Build Type: beryllium-user
Build Number: PKQ1.180729.001
Incremental: V11.0.5.0.PEJMIXM
Tags: release-keys
Security Patch: 2019-10-01
Fingerprint: Xiaomi/beryllium/beryllium:9/PKQ1.180729.001/V11.0.5.0.PEJMIXM:user/release-keys
Description: beryllium-user 9 PKQ1.180729.001 V11.0.5.0.PEJMIXM release-keys
Raw Image Size: 2.49 GiB
Clean Installation
Step:
1. flash latest Firmware https://mega.nz/#!QDplSYab!mrB5f8875VghQHfrrGvid4iJICMopkq3anZCipLWzqo
2. flash Vendor https://mega.nz/#!ECAG1aIS!OuGf9eVoiJpg0xreeLIarAWs5GkuCbu9AwR95MSlO-g
3. flash GSI as System Image
4. flash Permissiver v4.zip https://mega.nz/#!ETIwHQJC!Go5NfpgXFy5gPw8gFG8JbUCch7Eijw4rDp3NVTkhd-M
5. flash Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip https://mega.nz/#!gTohmQaR!ZL5jCeatYXUzUMx_moJseJ9o7b1RoLUf3o_PfOtn_aw
--Mount System & Vendor
6. flash Sound Fix (fixaudiogsi.zip) https://mega.nz/#!AD52wIhD!FM5GruKjw76gRnXqqLrh73CsSIZmldANlZrzyfVlcX0
7. flash DropVendorLightHAL.zip https://mega.nz/#!QKgVxaCI!lJuYDA2HjpP8msTbB7uXzW5jlvHImmHBtjjAdjt5R5g
8. flash DisableForceEncryption_Treble_v20.1.zip https://mega.nz/#!BHgRWYDS!jfuIRqTPTjS_lVy2tfpSbVRfqmxqqadeLFttgbKmhYQ
Reboot
-Verify your MI Account.
1.connect your WiFi 2. input you mi password. ...wait
- Magisk manager add MIUI_Auto_Brightness_Fix_v4_(pie).zip
https://mega.nz/#F!hT5UkSAQ!VCiS_BVC0Jlobpo6EMLsDg
-install GMS.apk and reboot
Coming soon --- Fingerprint Fix
Click to expand...
Click to collapse
Hello, I installed this version, in <Additional Settings>, <Region>, it shows "CHINA" and I can't change to my "Brazil" region. How do I change?
evanderfreitas said:
Hello, I installed this version, in <Additional Settings>, <Region>, it shows "CHINA" and I can't change to my "Brazil" region. How do I change?
Click to expand...
Click to collapse
I don't think u can. But it doesn't change much anyway. I dont think it has Portuguese
Works well but..
That's the only rom i found that is smooth, and have dark mode
also the only one with Miui11 that support sdcard slot
So thanks a lot!! :good::good:
The only problem is that everything on the screen is too big, even if i reduce it with display settings or other settings.
Is there anything we can do ? Like flashing a zip with magisk that'll change that?
nabilrezki said:
That's the only rom i found that is smooth, and have dark mode
also the only one with Miui11 that support sdcard slot
So thanks a lot!! :good::good:
The only problem is that everything on the screen is too big, even if i reduce it with display settings or other settings.
Is there anything we can do ? Like flashing a zip with magisk that'll change that?
Click to expand...
Click to collapse
Just change dpi of the screen to 600 dp through developer settings
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
nizdi said:
Tom, thanks for everything you have done.
Only one question: when you fix fingerprint, will we have to flash whole system again or maybe only a part of it? Reading mode going to be fixed? (block blue light,useful to study)
thanks.
Edit:
@nirh216
Dude, in the bottom side, right side, there's a option to image file. click it, then choose the huge file (about 2gb) you donwloaded and flash it.
Edit2: Physical home button it's kinda useless to unlock right now, right? I cant see to use it even to unlock it, only as "home button". And i did not installed fix for auto brightness because mine is working, and i could not find how to install it by magisk, if anyone has atuto for it. thanks.
Edit3: 2 bugs I found. 1st Nav bar stop working after a while, needing to restart device to work. 2nd brightness from screen is definetly low, like half the bright from normal stock rom ----> I guess brightness is a problem from pocophone and about nav bar seems like tasker was fckng it up
Thanks.
Edit4: last edit lol. My twrp seems to be gone after doing every step and i cant find to install it again. you guys have twrp working?
Click to expand...
Click to collapse
No problem with twrp
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?
Removed
Instructions can be found in the README on GitHub: https://github.com/Miustone/MARS_SOM
BETA4 uploading with some fixes and enhancements. Thanks to My Discord Channel and all the nice People keeping Me up! :angel:
@cd993 for being My (coming) Tester!
Is this rom even for the dual sim XQ-AT52 version?
Gigio755 said:
Is this rom even for the dual sim XQ-AT52 version?
Click to expand...
Click to collapse
It's a unified SOM for all Xperia Variants with API29 and Snapdragon SoCs. So yes :good:
My shared Kernels for Magisk are for and from the EU Firmware of the Xperias btw.
Just to add my experience here, I flashed this rom magisk module which entered a seemingly unrecoverable endless bootloop. This was likely as it conflicted with another magisk module or xposed that I have installed, so not the fault of the rom!
However given we've no twrp yet, the best way (after a LOT of research!) to fix this wasn't easy or obvious. I thought I could just flash stock kernel, uninstall magisk, flash magisk again and uninstall the module. Which unfortunately you can't as they remain in the system files and without root, you can't touch them, though with root, it loads and you get the bootloop - so a vicious endless cycle!
The solution I managed to work out, rather than a full clean wipe was to extract the stock boot from downloaded firmware (using Xperifirm), convert it to an img file using unsin (Google this if needed) and then use Android kitchen to unpack, place a certain folder in there (found via the link below), repack and then fastboot flash. This makes magisk operate in core root mode only allowing you to uninstall the module. Once the module is uninstalled, you can simply disable core only mode from the magisk settings.
This saved me from a full wipe!
See here for more details about that unpacking etc
https://forum.xda-developers.com/pi...modules-disabler-booting-magisk-t3976621/amp/
cd993 said:
Just to add my experience here, I flashed this rom magisk module which entered a seemingly unrecoverable endless bootloop. This was likely as it conflicted with another magisk module or xposed that I have installed, so not the fault of the rom!
However given we've no twrp yet, the best way (after a LOT of research!) to fix this wasn't easy or obvious. I thought I could just flash stock kernel, uninstall magisk, flash magisk again and uninstall the module. Which unfortunately you can't as they remain in the system files and without root, you can't touch them, though with root, it loads and you get the bootloop - so a vicious endless cycle!
The solution I managed to work out, rather than a full clean wipe was to extract the stock boot from downloaded firmware (using Xperifirm), convert it to an img file using unsin (Google this if needed) and then use Android kitchen to unpack, place a certain folder in there (found via the link below), repack and then fastboot flash. This makes magisk operate in core root mode only allowing you to uninstall the module. Once the module is uninstalled, you can simply disable core only mode from the magisk settings.
This saved me from a full wipe!
See here for more details about that unpacking etc
https://forum.xda-developers.com/pi...modules-disabler-booting-magisk-t3976621/amp/
Click to expand...
Click to collapse
Nice and complicated to Share! Thanks for Your Post! I would suggest next time to remove a specific File from the Firmware before flashing with NewFlasher which keeps Your Data intact. Let Me take a Look which one it was...
Edith: Remove userdata_X-FLASH-CUST-A2CD.sin before flashing or your data will be wiped.
Or in ur case userdata_BLAHBLAH.SIN
You can also try to enter Save Mode next time which works by Holding the Power Button while booting or so. Maybe together with VolumeDown and No USB connected.
Miustone said:
Nice and complicated to Share! Thanks for Your Post! I would suggest next time to remove a specific File from the Firmware before flashing with NewFlasher which keeps Your Data intact. Let Me take a Look which one it was...
Edith: Remove userdata_X-FLASH-CUST-A2CD.sin before flashing or your data will be wiped.
Or in ur case userdata_BLAHBLAH.SIN
You can also try to enter Save Mode next time which works by Holding the Power Button while booting or so. Maybe together with VolumeDown and No USB connected.
Click to expand...
Click to collapse
Ah that's very handy to know, thanks for the removal of userdata sin file tip!
cd993 said:
Ah that's very handy to know, thanks for the removal of userdata sin file tip!
Click to expand...
Click to collapse
You're Welcome ! And sorry for the Trouble. Looking Forward to fix everything... :angel:
Good to see development starting!
Hopefully something can be done with the cameras viewfinder which appears really poor than the shot actually being taken! Snapchat looks awful when taking video selfies
dreamville said:
Good to see development starting!
Hopefully something can be done with the cameras viewfinder which appears really poor than the shot actually being taken! Snapchat looks awful when taking video selfies
Click to expand...
Click to collapse
Agreed. I look like I'm wearing makeup on WhatsApp video calls!
Hello, dear developer.
Miustone said:
You're Welcome ! And sorry for the Trouble. Looking Forward to fix everything... :angel:
Click to expand...
Click to collapse
Hello, respected developer. (XQ-AT52) I am a user. I installed the rom after patching the boot.img extracted from two versions, the Taiwan version and the Hong Kong version, but both fall into infinite boot twice. Should I use the EU single SIM version?
---------- Post added at 03:57 PM ---------- Previous post was at 03:55 PM ----------
Hello, respected developer. (QX-AT52) I am a user. I installed the rom after patching the boot.img extracted from two versions, the Taiwan version and the Hong Kong version, but both fall into infinite boot twice. Should I use the EU single SIM version?
htcmage said:
Hello, respected developer. (XQ-AT52) I am a user. I installed the rom after patching the boot.img extracted from two versions, the Taiwan version and the Hong Kong version, but both fall into infinite boot twice. Should I use the EU single SIM version?
---------- Post added at 03:57 PM ---------- Previous post was at 03:55 PM ----------
Hello, respected developer. (QX-AT52) I am a user. I installed the rom after patching the boot.img extracted from two versions, the Taiwan version and the Hong Kong version, but both fall into infinite boot twice. Should I use the EU single SIM version?
Click to expand...
Click to collapse
You could, but im working on the Support for the Mark 2 actually. Sadly am i unable to extract the Firmware of it. Could you Help me Out with a dump?
Miustone said:
[...] Sadly am i unable to extract the Firmware of it. Could you Help me Out with a dump?
Click to expand...
Click to collapse
UnSIN *super*.sin to get the img file, and 7zip to extract img contents ( windows: right click > open > # | linux: UnSIN thread, read up "Note: super_*.img ..." ).
Stock camera, Cinema Pro, Photo Pro all gone in this ROM or working just fine?
serajr said:
UnSIN *super*.sin to get the img file, and 7zip to extract img contents ( windows: right click > open > # | linux: UnSIN thread, read up "Note: super_*.img ..." ).
Click to expand...
Click to collapse
Honored to get that Reply from You. Know Your Work Well since many Years :good: I will try 7Zip now:fingers-crossed:
Onepunchbro said:
Stock camera, Cinema Pro, Photo Pro all gone in this ROM or working just fine?
Click to expand...
Click to collapse
It should work just fine. At least does Cinema Pro on the Xperia 1 and 5. Photo Pro will be Something to Port for 2019 Xperias but isn't touched or removed yet...
Miustone said:
Feature List:
(Not everything is listed)
Full Camera API2
Full Pixel User Interface
Ported Pixel 4 XL Apps
Ported Pixel 4 XL Features
Click to expand...
Click to collapse
I've never used a SOM ROM and I'm a bit confused on what you mean by "full camera API2".
Stock, the Xperia 1 ii only has FULL Camera2 API support and RAW output for the main 24mm camera. All other cameras have LIMITED Camera2 API support and no RAW support.
Does the SOM ROM somehow enable FULL Camera2 API and RAW for all lenses on the phone?
Sent from my SM-G965F using Tapatalk
fuzzybabybunny said:
I've never used a SOM ROM and I'm a bit confused on what you mean by "full camera API2".
Stock, the Xperia 1 ii only has FULL Camera2 API support and RAW output for the main 24mm camera. All other cameras have LIMITED Camera2 API support and no RAW support.
Does the SOM ROM somehow enable FULL Camera2 API and RAW for all lenses on the phone?
Sent from my SM-G965F using Tapatalk
Click to expand...
Click to collapse
Yes, there is advanced support present for Open Camera for example allowing You to use all API2 Features on all Sensors including the Front Camera.
V20071 comes soon btw. Website and GitHub are getting Updates too...
BR
Does using custom on latest generation Xperia Phone still erases some sort of Camera DRM and in the end users are getting downgraded camera performance like in the past Xperias? Or such thing are no longer the case and it is perfectly safe to use custom ROM and switch back to stock ROM whenever needed?
Great Developer
Great Developer, can I ask you one more thing? Unlike Xperia 1& products, Qualcomm's diagnostic port activation order does not apply. (setprop sys.usb.config rndis,eng_mode,adb ) Can you help me with the development of the command? It's small, but I'll definitely sponsor you.
** Standard Disclaimer: Unlocking your Bootloader will Void your Warranty. I take no responsibility for this or for any bricked devices. These thing should go without saying at this point, but there they are. If you are here, I assume you are familiar with LineageOS, TWRP, and moving from MIUI to AOSP-based ROMs**
I've built a clean version of LineageOS 17.1 for Mi 9 that includes Signature Spoofing, but no other modifications.
This will allow those who are interested to get full MicroG support without the need of using any sort of Patcher or Magisk/XPosed Module. YOu all may have used my previous LineageOS Clean,Stock ROM and this is just an updated build of that ROM + Signature Spoofing to make life easier for those who want MicroG.
I flashed this and followed the simple steps of installing F-Droid, adding the MicroG Repo, and Installing the necessary packages via F-Droid and confirmed MicroG Self-check passes all the tests (once you finish granting the necessary permissions for each).
I prefer this over the NanoDroid or other patching methods as a much cleaner way to use MicroG with LineageOS.
Proprietary Blobs/Device Tree are DRG-Developer's as referenced in their post: here
Kernel source is by DRG-Developer: here
Xiaomi Hardware package used is the primary LineageOS from their github here
My reason for this is that there does not seem to be an officially-supported build for our device on the LineageOS for MicroG project or a recent, unofficial build.
What Works:
Pretty much everything from what I can tell
Fingerprint Sensor it working like a champ so far.
DT2W/DT2S
NFC Seems to be working but I don't have a device to test against
Known Issues:
You tell me...
Download:
849.98 MB file on MEGA
mega.nz
Prerequisite:
Make sure you are running a current AOSP/MIUI ROM with the latest firmware flashed and TWRP Installed
Install:
From TWRP:
1) Wipe Date (standard wipe)
2) Format Date ---> 'yes'
3) push ROM zip to /sdcard/
4) Flash ROM zip
4b) - OPTIONAL - Flash Magisk Zip for Root
5) Reboot to system
If you want to to install MicroG, just follow the steps outlined here in the "Install" section to get F-Droid installed, add the MicroG Repo, and install the handful of apps needed. No need for any of the patching steps.
DRG-Developer's device trees were last updated on 2020-10-18 so expect this build to reflect that. So far everything seems to function very well.
Does it support GApps too or it's only for MicroG?
Edit:
I test it and It's working well with GApps
Thanks for your build.
Vogie said:
Does it support GApps too or it's only for MicroG?
Edit:
I test it and It's working well with GApps
Thanks for your build.
Click to expand...
Click to collapse
Thanks for testing! If you find any bugs, please post them here. I may not be able to troubleshoot everything but at least other users will be aware.
What changes between your older release of LineageOS 17.1? https://forum.xda-developers.com/t/...ineageos-17-1-clean-stock-2020-07-10.4041523/
ICanTrollU said:
What changes between your older release of LineageOS 17.1? https://forum.xda-developers.com/t/...ineageos-17-1-clean-stock-2020-07-10.4041523/
Click to expand...
Click to collapse
Later/updated device trees and built-in Signature Spoofing that you don't get with stock Lineage.
photonmedia said:
Thanks for testing! If you find any bugs, please post them here. I may not be able to troubleshoot everything but at least other users will be aware.
Click to expand...
Click to collapse
Sure,
I'm using this ROM for daily use since yesterday and seems like very stable since now and battery life is good.
I missed `Internet Band-with Speed indicator` and `three finger swipe screen shot gesture` that I think these features are not available in LineageOS.
Vogie said:
Sure,
I'm using this ROM for daily use since yesterday and seems like very stable since now and battery life is good.
I missed `Internet Band-with Speed indicator` and `three finger swipe screen shot gesture` that I think these features are not available in LineageOS.
Click to expand...
Click to collapse
Yes, I do not believe those are included in stock LineageOS.
photonmedia said:
Yes, I do not believe those are included in stock LineageOS.
Click to expand...
Click to collapse
I didn't find any issue that relate to ROM, it's quite stable
I just have a issue on ANXCamera self camera that force close the ANXCamera that I think is not related to ROM
photonmedia said:
...
What Works:
...
NFC Seems to be working but I don't have a device to test against
Click to expand...
Click to collapse
This morning I checked NFC by sending a picture from my MI 9 to my wife's Mi 9T (also equipped with LOS). The transfer was successfull!
Thank you very much for providing this clean (stock) ROM!
Hi,
I've just unlocked my device and flashed Mauronofrio's TWRP afer that, i've installed this rom. And everytime it seems to be bootlooping. Showing the MI logo and after that it turns off and goes back to the Mi logo again. I've tried flashing it a few times, wiping data / system ETC. At the moment I'm restoring it with flashtool to get it back working. But am I doing something wrong?
nico445 said:
Hi,
I've just unlocked my device and flashed Mauronofrio's TWRP afer that, i've installed this rom. And everytime it seems to be bootlooping. Showing the MI logo and after that it turns off and goes back to the Mi logo again. I've tried flashing it a few times, wiping data / system ETC. At the moment I'm restoring it with flashtool to get it back working. But am I doing something wrong?
Click to expand...
Click to collapse
Did you wipe data AND "Format" Data? When you Format data is asks you to confirm by typing "yes" in the TWRP Recovery. Try Wiping and Formatting data, then push the ROM to the phone and Flash.
Ah that was probably it. ADB Sideload wasn't co-operating so i've flashed the rom first and after that wiped + formatted the data. Thanks! I've just restored the phone but will try this later again.
nico445 said:
Ah that was probably it. ADB Sideload wasn't co-operating so i've flashed the rom first and after that wiped + formatted the data. Thanks! I've just restored the phone but will try this later again.
Click to expand...
Click to collapse
Also, be sure you are coming from an updated ROM running current firmware.
Thank for your build ;-)
Are NFC Payements working on it?
john_matrix said:
Thank for your build ;-)
Are NFC Payements working on it?
Click to expand...
Click to collapse
I have not tested payments. Another user confirmed that file transfer via NFC works. I do not use NFC for payments so cannot test.
Hi, does screen off fod work?
Your rom is really simple stock rom, but there is something that I can't make it work. Waze has been my pain, the map dont load and I cant make it run. Anyway you did a good job. You discovered how can we put updates in the rom?
theandroid02 said:
Hi, does screen off fod work?
Click to expand...
Click to collapse
No, you have to double-tap to wake or hit the power button to wake the screen before you can use the fingerprint scanner.
Vinicius7 said:
Your rom is really simple stock rom, but there is something that I can't make it work. Waze has been my pain, the map dont load and I cant make it run. Anyway you did a good job. You discovered how can we put updates in the rom?
Click to expand...
Click to collapse
After installing, did you Install F-Droid and enable the Magisk repositories to install the necessary Magisk Modules and Location Backends? Then in the MicroG settings ensure all the checkboxes are checked?
Thanks for making this ROM. Really appreciate it.
The only small issue I am noticing is that my finance apps (example: banking apps, stock trading apps) popup an alert saying that my device is rooted (even though it is not) and this could be a security risk. The apps do still function but its a bit annoying to see this alert every time I launch the app.
Is this because the ROM has been signed with public keys? This alert does not appear when I used the iode OS ROM for Mi 9 or when I use the official Lineage OS for MicroG ROM on my Mi 8.
dmahtani said:
Thanks for making this ROM. Really appreciate it.
The only small issue I am noticing is that my finance apps (example: banking apps, stock trading apps) popup an alert saying that my device is rooted (even though it is not) and this could be a security risk. The apps do still function but its a bit annoying to see this alert every time I launch the app.
Is this because the ROM has been signed with public keys? This alert does not appear when I used the iode OS ROM for Mi 9 or when I use the official Lineage OS for MicroG ROM on my Mi 8.
Click to expand...
Click to collapse
I'm not sure. It could be the Signature Spoofing aspect. I don't think iode has that and I know stock LIneage does not.
Do you have Magisk installed?