Thought i should let you know that WE HAVE a WORKING METHOD for flashing APPROVED firmwares listed on Firmware Finder!
PLEASE, READ the OP + HOW TO 3 times before proceeding, so that way we avoid unpleasant flash situations, like those when users flashed P30 Pro firmwares on P30 devices or vice versa
WE CAN USE ONLY APPROVED FullOTA.zip firmwares using links from Firmware Finder (Android version / DESKTOP version). It will work 100% if you will follow the instructions bellow to the letter!
BE ADVISED!
A. Keep in mind that you are going to flash a newer version that maybe is not yet released for your region and could result in having to Factory Reset your phone. Also it’s possible that the firmware will not pass Safety Net Test! and therefore some apps could stop working or not appear as available for installing on Google Play! It’s safer to flash a newer version ONLY after you’ve read that someone else has received it by OTA in the same or different country OR I update OP with that info. Always BACKUP before proceeding!
B. The method described bellow is intended to be used on updating on LOCKED BOOTLOADER by using Huawei HiSuite alongside a great app created by @IProfessor, the dev who coded HISuite Proxy to be used on Huawei devices – THANKS to @IProfessor for your excellent app & to @nomone for letting me know about this release.
I'm not responsible for bricked devices, dead Huawei NM cards or any other problems that can appear if you flashed wrong versions!!!
Latest VOG-L29 C10 / VOG-L09 C431 / VOG-L29 C431 / VOG-L29 C432 / VOG-L29 C675 firmware link is for v10.1.0.195, added on 07.01.2021, with December SP as chengelog.
Latest VOG-L04 C69, VOG-L04 C605, VOG-L29 C185, VOG-L29 C461 & VOG-L29 C605 firmware link is for v10.1.0.163, added on 11.10.2020.
HOW TO FLASH for VOG devices :
1. Download and use ONLY this version from my Gdrive, HiSuite_10.0.1.100_OVE ;
2. Download and unzip HISuite Proxy.
3. Open HISuite Proxy Application & click on "SETUP" button; after all "SETUP" process is done, check in Huawei HiSuite settings if the SETUP wrote the proxy configuration like Proxy Adress 127.0.0.1 and Port 7777, then proceed to next step;
4. Use the link corresponding to your cust as following:
____________________________________________________________________________________________________________
ONLY FOR VOG-L29 C10 / VOG-L09 C431 / VOG-L29 C431 / VOG-L29 C432 / VOG-L29 C675 (SAFETY NET PASSES) use as bellow:
ON Package URL copy following link (open link in browser and then copy URL) – http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v506966/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.195
ONLY FOR VOG-L29 C675 use as bellow:
ON Package URL copy following link (open link in browser and then copy URL) – http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v479659/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.177
ONLY FOR VOG-L04 C69, VOG-L04 C605, VOG-L29 C185, VOG-L29 C461 & VOG-L29 C605 use as bellow:
ON Package URL copy following link (open link in browser and then copy URL) - http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v464970/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.163
ONLY FOR VOG-L04 devices flash alongside Base firmware v163
ON CUST PKG (open link in browser and then copy URL) -
http://update.dbankcdn.com/TDS/data...1755/v463506/f1/full/changelog_cust_hw_la.xml
ON Point Version (tick box and write) : VOG-L04-CUST 10.0.0.22(C605)
Also, DON'T FORGET TO tick CUST PKG box under normal OS!
ONLY FOR VOG-L29 C636 use as bellow:
ON Package URL copy following link (open link in browser and then copy URL) – http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v433814/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.145
For VOG-L04 C792, PLEASE use links from this post #1214.
___________________________________________________________________________________________________________
Make sure that CUST PKG & Preloaded PKG boxes are blank for when you flash ONLY PACKAGE URL (see SS bellow OP), same where is written BLA (remove any words from right side, on CUST PKG & Preloaded PKG)!
5. Check Normal OS;
6. OPEN Huawei HiSuite, connect it to your phone (be sure that HiSuite Proxy remains OPENED ALL THE PROCESS) and check for an update. You will be prompted to update to latest available (according to the link you've used) Hit OK and let HiSuite download and install the update. After successful update, your phone will restart and you can close HiSuite Proxy.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ALL released EMUI 10.1 firmware links can be found bellow!
EMUI 10.1 BASE firmware for P30 PRO (VOG-L09 / VOG-L29) devices:
FLASH ONLY ON P30 PRO (VOG-L09 / VOG-L29), OTHERWISE YOU WILL GET SOFTBRICK
Version 10.1.0.169 is only for VOG-L29 C675:
ON Package URL copy following link (open link in browser and then copy URL) – http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v473411/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.169
Version 10.1.0.166 is only for VOG-L29 C675:
ON Package URL copy following link (open link in browser and then copy URL) – http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v462514/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.166
Version 10.1.0.163 is only for VOG-L04 C69, VOG-L04 C605, VOG-L29 C185, VOG-L29 C461 & VOG-L29 C605:
ON Package URL copy following link (open link in browser and then copy URL) - http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v464970/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.163
Version 10.1.0.161 is only for VOG-L29 C431 & VOG-L29 C432:
ON Package URL copy following link (open link in browser and then copy URL) – http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v470222/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.161
Version 10.1.0.156 with July SP is only for VOG-L29 C431 / VOG-L29 C432:
ON Package URL copy following link (open link in browser and then copy URL) - http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v441612/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.156
Version 10.1.0.152 is only for VOG-L29 C675:
ON Package URL copy following link (open link in browser and then copy URL) – http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v444913/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.152
Version 10.1.0.151 is only for VOG-L04 C69, VOG-L04 C605, VOG-L29 C185, VOG-L29 C461 & VOG-L29 C605:
ON Package URL copy following link (open link in browser and then copy URL) - http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v445128/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.151
Version 10.1.0.150 with August SP is only for VOG-L09 C431 / VOG-L29 C431 & VOG-L29 C432:
ON Package URL copy following link (open link in browser and then copy URL) - http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v446036/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.150
Version 10.1.0.146 is only for VOG-L29 C675:
ON Package URL copy following link (open link in browser and then copy URL) – http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v436243/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.146
Version 10.1.0.145 is only for VOG-L29 C636:
ON Package URL copy following link (open link in browser and then copy URL) – http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v433814/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.145
Version 10.1.0.141 is only for VOG-L04 C605, VOG-L29 C185, VOG-L29 C461 & VOG-L29 C605:
ON Package URL copy following link (open link in browser and then copy URL) - http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v428543/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.141
Version 10.1.0.140 is only for VOG-L09 C431 & VOG-L29 C431 / VOG-L29 C432:
ON Package URL copy following link (open link in browser and then copy URL) - http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v433349/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.140
Version 10.1.0.133 is only for VOG-L09 C431 & VOG-L29 C431 / VOG-L29 C432:
ON Package URL copy following link (open link in browser and then copy URL) – http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v423284/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.133
Version 10.1.0.126 is only for VOG-L29 C185, VOG-L29 C636 & VOG-L29 C605:
ON Package URL copy following link (open link in browser and then copy URL) - http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v413141/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.126
For VOG-L04 C792, PLEASE use links from this post #1214.
For VOG-L04 C25, PLEASE use links from this post #525.
Version 10.1.0.123 is only for VOG-L09 C431 & VOG-L29 C431 / VOG-L29 C432:
ON Package URL copy following link (open link in browser and then copy URL) - http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v410289/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.123
Patch 02 ON Package URL copy following link (open link in browser and then copy URL) - http://update.dbankcdn.com/TDS/data/files/p3/s15/G5731/g1755/v408063/f1/full/changelog.xml
ON Point Version you have to tick it and write : VOG-LGRP2-OVS 10.1.0.123(patch02)
EMUI 10.1 BASE firmwares for P30 (ELE-L09/ELE-L29) devices:
For video tutorial (be advised that it has P30 (ELE) links on it, so if you're gonna use a P30 PRO device, use VOG links instead), watch this video! thanks @Alexxxx1 for creating & share it!
FLASH ONLY ON P30 (ELE-L09 / ELE-L29), OTHERWISE YOU WILL GET SOFTBRICK
Version 10.1.0.150 is only for ELE-L09 C431 & ELE-L29 C431 / ELE-L29 C432
ON Package URL copy following link (open link in browser and then copy URL) – http://update.dbankcdn.com/TDS/data/files/p3/s15/G5625/g1755/v446203/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : ELE-LGRP2-OVS 10.1.0.150
Version 10.1.0.140 is only for ELE-L09 C431 & ELE-L29 C431 / ELE-L29 C432
ON Package URL copy following link (open link in browser and then copy URL) – http://update.dbankcdn.com/TDS/data/files/p3/s15/G5625/g1755/v434974/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : ELE-LGRP2-OVS 10.1.0.140
Version 10.1.0.133 is only for ELE-L09 C431 & ELE-L29 C431 / ELE-L29 C432
ON Package URL copy following link (open link in browser and then copy URL) – http://update.dbankcdn.com/TDS/data/files/p3/s15/G5625/g1755/v423641/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : ELE-LGRP2-OVS 10.1.0.133
Version 10.1.0.126 is working on ELE-L04 C69 & ELE-L29 C605:
ON Package URL copy following link (open link in browser and then copy URL) - http://update.dbankcdn.com/TDS/data/files/p3/s15/G5625/g1755/v411960/f1/full/changelog_base.xml
ON Point Version you have to tick it and write : ELE-LGRP2-OVS 10.1.0.126
Version 10.1.0.123 is working on ELE-L09 C431 & ELE-L29 C431 / ELE-L29 C432:
ON Package URL copy following link (open link in browser and then copy URL) - http://update.dbankcdn.com/TDS/data/files/p3/s15/G5625/g1755/v406323/f1/full/filelist.xml
ON Point Version you have to tick it and write : ELE-LGRP2-OVS 10.1.0.123
Patch 01 ON Package URL copy following link (open link in browser and then copy URL) - http://update.dbankcdn.com/TDS/data/files/p3/s15/G5625/g1755/v414292/f1/full/changelog.xml
ON Point Version you have to tick it and write : ELE-LGRP2-OVS 10.1.0.123(patch01)
Patch 03 ON Package URL copy following link (open link in browser and then copy URL) - http://update.dbankcdn.com/TDS/data/files/p3/s15/G5625/g1755/v414188/f1/full/changelog.xml
ON Point Version you have to tick it and write : ELE-LGRP2-OVS 10.1.0.123(patch03)
That’s all, folks! Right now you should have updated to latest FIRMWARE available for your device! I will update OP with new BASE firmwares as soon as they will get approved & tested, so SUBSCRIBE to this thread so you'll be updated!
thanks friend. let's see how this goes
NOT WORKING as of 01.12.2020
CUST & PRELOAD PKG's for SOFTWARE CUST REBRAND
In this post i will share links for CUST & PRELOADS that you could use to SOFTWARE REBRAND (CHANGE YOUR ORIGINAL CUST to another one from a different zone) a broken cust device or a C900 one.
HOW TO CHANGE IT - BE AWARE IT MIGHT FACTORY RESET DEVICE OR Safety Net Pass to fail!, so flash at your OWN RISK!
1. DO ALL the steps from 1-4 that are written in OP! then proceed to next step;
2. Use any of the Cust & Preload bellow toghether when flashing; DON'T FLASH C431 Cust PKG & C432 Preloaded PKG, it will fail or worse, softbrick device!
ONLY FOR VOG-L29 devices use packages as follow :
C431 CUST & PRELOAD PKG's
CUST PKG (open link in browser and then copy URL to HiSuite app) -
http://update.dbankcdn.com/TDS/data...755/v329470/f1/full/changelog_cust_hw_eea.xml
Point Version (thick box and write) : VOG-L29-CUST 10.0.0.19(C431)
Preloaded PKG (open link in browser and then copy URL to HiSuite app) -
http://update.dbankcdn.com/TDS/data...51154/f1/full/changelog_preload_hw_eea_R2.xml
Point Version (thick box and write) : VOG-L29-PRELOAD 10.0.0.5(C431R2)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
C432 CUST & PRELOAD PKG's
CUST PKG (open link in browser and then copy URL to HiSuite app) -
http://update.dbankcdn.com/TDS/data...1755/v351139/f1/full/changelog_cust_hw_eu.xml
Point Version (thick box and write) : VOG-L29-CUST 10.0.0.19(C432)
Preloaded PKG (open link in browser and then copy URL to HiSuite app) -
http://update.dbankcdn.com/TDS/data...351140/f1/full/changelog_preload_hw_eu_R2.xml
Point Version (thick box and write) : VOG-L29-PRELOAD 10.0.0.5(C432R2)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
C461 CUST & PRELOAD PKG's
CUST PKG (open link in browser and then copy URL to HiSuite app) -
http://update.dbankcdn.com/TDS/data...755/v414544/f1/full/changelog_cust_hw_cea.xml
Point Version (thick box and write) : VOG-L29-CUST 10.1.0.11(C461)
Preloaded PKG (open link in browser and then copy URL to HiSuite app) -
http://update.dbankcdn.com/TDS/data...52370/f1/full/changelog_preload_hw_cea_R1.xml
Point Version (thick box and write) : VOG-L29-PRELOAD 10.0.0.3(C461R1)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
C185 CUST & PRELOAD PKG's
CUST PKG (open link in browser and then copy URL to HiSuite app) -
http://update.dbankcdn.com/TDS/data...v350673/f1/full/changelog_cust_hw_meafnaf.xml
Point Version (thick box and write) : VOG-L29-CUST 10.0.0.8(C185)
Preloaded PKG (open link in browser and then copy URL to HiSuite app) -
http://update.dbankcdn.com/TDS/data...3/f1/full/changelog_preload_hw_meafnaf_R3.xml
Point Version (thick box and write) : VOG-L29-PRELOAD 10.0.0.1(C185R3)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
C605 CUST & PRELOAD PKG's
CUST PKG (open link in browser and then copy URL to HiSuite app) -
http://update.dbankcdn.com/TDS/data...1755/v351585/f1/full/changelog_cust_hw_la.xml
Point Version (thick box and write) : VOG-L29-CUST 10.0.0.19(C605)
Preloaded PKG (open link in browser and then copy URL to HiSuite app) -
http://update.dbankcdn.com/TDS/data...351586/f1/full/changelog_preload_hw_la_R1.xml
Point Version (thick box and write) : VOG-L29-PRELOAD 10.0.0.3(C605R1)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
C636 CUST & PRELOAD PKG's
CUST PKG (open link in browser and then copy URL to HiSuite app) -
http://update.dbankcdn.com/TDS/data...v396050/f1/full/changelog_cust_hw_spcseas.xml
Point Version (thick box and write) : VOG-L29-CUST 10.0.0.10(C636)
Preloaded PKG (open link in browser and then copy URL to HiSuite app) -
http://update.dbankcdn.com/TDS/data...1/f1/full/changelog_preload_hw_spcseas_R1.xml
Point Version (thick box and write) : VOG-L29-PRELOAD 10.0.0.3(C636R1)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
C675 CUST & PRELOAD PKG's
CUST PKG (open link in browser and then copy URL to HiSuite app) -
http://update.dbankcdn.com/TDS/data...1755/v352720/f1/full/changelog_cust_hw_in.xml
Point Version (thick box and write) : VOG-L29-CUST 10.0.0.4(C675)
Preloaded PKG (open link in browser and then copy URL to HiSuite app) -
http://update.dbankcdn.com/TDS/data...355615/f1/full/changelog_preload_hw_in_R3.xml
Point Version (thick box and write) : VOG-L29-PRELOAD 10.0.0.2(C675R3)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
3. Check Normal OS (left side of app, under Proxy Address ) and bellow it thick also those 2 boxes - CUST PKG & Preloaded PKG.
4. OPEN HiSuite, connect it to your phone (be sure that HiSuite Proxy remains OPENED ALL THE PROCESS) and check for an update. You will be prompted to update to latest available. Hit OK and let HiSuite download and install the update. After succesfull update, phone will restart and you can close HiSuite Proxy app.
Thanks man for spreading the app, I'm really glad to see it working and helping people out, I'll try to update it regularly hoping for better and easier features. (I've already fixed the patching method, which was confusing a lot of people lol, it was like that because I didn't want the app to run as admin, as that's really dangerous and might bring concerns for people, now it runs as admin only for milliseconds when it wants to replace the patched httpcomponent.dll with original one... Version 1.7.5)
Cheers ?
IProfessor said:
Thanks man for spreading the app, I'm really glad to see it working and helping people out, I'll try to update it regularly hoping for better and easier features. (I've already fixed the patching method, which was confusing a lot of people lol, it was like that because I didn't want the app to run as admin, as that's really dangerous and might bring concerns for people, now it runs as admin only for milliseconds when it wants to replace the patched httpcomponent.dll with original one... Version 1.7.5)
Cheers ?
Click to expand...
Click to collapse
Thanks for letting me know, i will update OP. Your newest version, v1.7.5 is allready linked on my OP.
Thanks again for this GREAT APP and for the chance you've given to us, P30 / P30 Pro users who had no way of updating using OTA firmware untill these days, when you created the app.
Keep on doing great things, m8!
Sent from my VOG-L29 using XDA Labs
SilviuO said:
, one more step needed, the link for the EMUI 10.1 firmware from Firmware Finder :highfive:
Sent from my VOG-L29 using XDA Labs
Click to expand...
Click to collapse
Can I try version 208, 210 ...?
Thanks
SilviuO said:
Hi guys,
I thought i should let you know that WE HAVE a WORKING METHOD for flashing FullOTA's zip from Firmware Finder!
This thread is
UNDER CONSTRUCTION and will be updated with SS and FullOTA.zip base package link
as soon as the firmware will be available on Firmware Finder.
You can download anyAPPROVED FullOTA update.zip from Firmware Finder (Android version / ON-Line version or PC version) and flash it on your device. Currently it works 100% if you follow the instructions bellow to the letter ! ! !
BE AWARE !
A. Keep in mind that you are going to flash a newer version that maybe is not yet released for your region and could result in having to reset your phone or an unstable system. Also it’s possible that the firmware might not be verified yet by Google (won’t pass the Google certification, so you will not be able to install Netflix or other apps that requires to be Google certified) and therefore some apps could stop working or not appear as available for installing. Most of the time it’s safe to flash a newer version after you’ve read that someone has received it by OTA in the same or different country. When i tested on EMUI 10 with firmware v10.0.0.208 no wipe was done. I was coming from EMUI 10 v10.0.0.195, but this is no insurance that it will never wipe your phone, so backup always before proceeding ! ! !
B. The method described bellow is intended to be used on updating from EMUI 10 to EMUI 10.1 on LOCKED BOOTLOADER by using HiSuite from Huawei and one app created by @IProfessor, the dev who coded HISuite Proxy to be used on Huawei devices – THANKS to @IProfessor for your excellent app & to @nomone for letting me know about this update method.
C. Firmwares links are the ones got from Firmware Finder and are OFFICIAL FullOTA’s base packages, CUST & PRELOAD zips. Flash ONLY APPROVED FOR YOUR DEVICE FIRMWARES, otherwise it will not succeed and might get softbricked !
IMPORTANT: In order to update ON THE SAME ANDROID version and not performing an upgrade like EMUI 10 to EMUI 10.1, you only need to use Package URL (FullOTA update zip / base zip) on step 5 + 6 and only "Point Version" ticked, no need to use CUST & PRELOAD!
HOW TO USE
1. Download and Install Hisuite ;
2. Download and unzip HISuite Proxy ;
3. Open HISuite Proxy Application. Click on "HTTP Component" button. Choose "httpcomponent.dll" file which exists in HiSuite's folder from C:\Program Files (x86)\HiSuite and then choose a new folder to save the patched file inside it to replace it later or replace the old file with the new patched "httpcomponent.dll" when asked where to put the patched one;
4. Open HiSuite, go into the settings and set the proxy address to 127.0.0.1 and port 7777, then close it (even from Taskbar);
5. OPEN HIsuite Proxy app and use the following links ON it:
Package URL (FullOTA update zip / base zip) – LINK NOT YET AVAILABLE! WILL BE UPDATED!
CUST PKG URL – VOG-L29-CUST 10.0.0.19(C431)
Preloaded PKG URL - VOG-L29-PRELOAD 10.0.0.5(C431R2)
6. Then on the right side, in the case before "Point Version" you have to thick all 3 of them after you wrote as bellow :
Package – Build number NOT YET AVAILABLE! WILL BE UPDATED!
CUST PKG - VOG-L29-CUST 10.0.0.19(C431)
Preloaded PKG - VOG-L29-PRELOAD 10.0.0.5(C431R2)
7. Check Normal OS, CUST PKG, Preloaded PKG.
8. OPEN HiSuite, connect it to your phone (be sure that HiSuite Proxy remains OPENED ALL THE PROCESS) and check for an update. You will be prompted to update to latest available. Hit OK and let HiSuite download and install the update. After succesfull update, phone will restart and you can close HiSuite Proxy app.
That’s all, folks! Right now you should have updated to latest APPROVED FIRMWARE available for your device !!!
Goodluck flashing ! ! !
Click to expand...
Click to collapse
Great guide mate :angel: thanks
jandro00 said:
Can I try version 208, 210 ...?
Thanks
Click to expand...
Click to collapse
YES, any firmware that says it's approved for your IMEI on Firmware Finder (use mobile version and on Settings choose Show only Full OTA; then on web version check that one that has the same build&release date as yours)
Ex. To be written in right case and thick ''Point Version'' VOG-LGRP2-OVS 10.0.0.208
To be written in Package URL http://update.dbankcdn.com/TDS/data/files/p3/s15/G4705/g1755/v408687/f1/full/changelog_base.xml
Then follow step 8 and wait for download and install. But be aware, it might get you uncertified in Google Playstore
Sent from my VOG-L29 using XDA Labs
jandro00 said:
Can I try version 208, 210 ...?
Thanks
Click to expand...
Click to collapse
Yes. If you're already on Emui 10 no need to use cust and preload. Also, as SilviuO said, pay attention at SafetyNet. Even if the firmware is approved, it's not sure the firmware will pass it
@SilviuO I think 10.1 cust and preload will released. Or maybe they will remain the same and in this case I think it's not needed to use them again for the update
nomone said:
Yes. If you're already on Emui 10 no need to use cust and preload. Also, as SilviuO said, pay attention at SafetyNet. Even if the firmware is approved, it's not sure the firmware will pass it
@SilviuO I think 10.1 cust and preload will released. Or maybe they will remain the same and in this case I think it's not needed to use them again for the update
Click to expand...
Click to collapse
I thought about it, but without base firmware, i can't make any tests .
When it will be available, i will ask users that are on EMUI 10 v195 to update ONLY using base firmware. If it's OK, i will update OP and wait for EMUI 11 to add cust&preload ???
Sent from my VOG-L29 using XDA Labs
SilviuO said:
I thought about it, but without base firmware, i can't make any tests .
When it will be available, i will ask users that are on EMUI 10 v195 to update ONLY using base firmware. If it's OK, i will update OP and wait for EMUI 11 to add cust&preload ???
Click to expand...
Click to collapse
EMUI 11 :laugh: :laugh:
it's it work for p30 not pro version
kraker77 said:
it's it work for p30 not pro version
Click to expand...
Click to collapse
YES, any firmware that says it's approved for your IMEI on Firmware Finder (use mobile version and on Settings choose Show only Full OTA; then on web version check that one that has the same build&release date as yours)
Ex. v10.0.0.206 is approved for installing for ELE-LGRP2-OVS. To be written for your device in right case and thick ''Point Version'' ELE-LGRP2-OVS 10.0.0.206
To be written in Package URL http://update.dbankcdn.com/TDS/data/files/p3/s15/G4830/g1755/v409552/f1/full/changelog_base.xml
Then follow step 8 and wait for download and install. But be aware, it might get you uncertified in Google Playstore
Sent from my VOG-L29 using XDA Labs
Alexxxx1 said:
So, if I use for example build 206 which is made for Middle East C185 and force it in Husuite and flash on my current build 195 for EU region C432 what it may cause... Is my build number stay correct? Because on earlier models from experience if you flash wrong build no it triggered to change oeminfo from lets say c432 to c900 and stuck on that version and made big issues...
Poslato sa ELE-L29 pomoću Tapatoka
Click to expand...
Click to collapse
Ok, so if use other firmware from other cust WITHOUT CUST&PRELOAD, only FullOTA.zip, it will not change your cust, it will remain the same, it will flash without any issuses (need ONLY to be approved) BUT your firmware will be not certified by Google, so you will not pass the Safety Net check.
Sent from my VOG-L29 using XDA Labs
SilviuO said:
Ok, so if use other firmware from other cust WITHOUT CUST&PRELOAD, only FullOTA.zip, it will not change your cust, it will remain the same, it flash without any issuses (need ONLY to be approved) BUT your firmware will be not certified by Google, so you will not pass the Safety Net check.
Sent from my VOG-L29 using XDA Labs
Click to expand...
Click to collapse
Ok, so its important to escape flashing Cust i Preload if I want to try builds for other region, right? If I try to flash cust i preload for different region it can cause issues or it can not be flashed?
Poslato sa ELE-L29 pomoću Tapatoka
Alexxxx1 said:
Ok, so its important to escape flashing Cust i Preload if I want to try builds for other region, right? If I try to flash cust i preload for different region it can cause issues or it can not be flashed?
Poslato sa ELE-L29 pomoću Tapatoka
Click to expand...
Click to collapse
YES, and i think - untill further tests and when the FullOTA.zip will be available - that we might not need the cust&preload files to update to EMUI 10.1, because it uses the same files it used when updating from EMUI 9.1 to EMUI 10....But i will clarify that when the link will be available and do some tests ?
If you flash cust and preload from other custs (let's say C636 CUST&PRELOAD over C431 cust), you will get a software rebrand and you will change your actual cust to C636, BUT you will not receive OTA's anymore and in case of warranty it will not be valid. In order to get back to your original cust (if you moved to C636), you will need to flash ONLY C431 CUST&PRELOAD using HISuite Proxy, but i don't reccomend messing with cust
Sent from my VOG-L29 using XDA Labs
SilviuO said:
YES, and i think - untill further tests and when the FullOTA.zip will be available - that we might not need the cust&preload files to update to EMUI 10.1, because it uses the same files it used when updating from EMUI 9.1 to EMUI 10....But i will clarify that when the link will be available and do some tests [emoji51]
If you flash cust and preload from other custs (let's say C636 CUST&PRELOAD over C431 cust), you will get a software rebrand and you will change your actual cust to C636, BUT you will not receive OTA's anymore and in case of warranty it will not be valid. In order to get back to your original cust (if you moved to C636), you will need to flash ONLY C431 CUST&PRELOAD using HISuite Proxy, but i don't reccomend messing with cust
Sent from my VOG-L29 using XDA Labs
Click to expand...
Click to collapse
Thank You for very detailed explanation. I hope that people will read carfelly your tutorial which is detailed too. Great Job SilviuO! [emoji106][emoji482]
Poslato sa ELE-L29 pomoću Tapatoka
I have succeeded. It does not work without loading the cust and preload files. I did the test yesterday and it didn't work. Today I understood it better and ready many thanks friends
I tried to upload an image, but I could not.
Now i have version 210 :fingers-crossed:
jandro00 said:
I have succeeded. It does not work without loading the cust and preload files. I did the test yesterday and it didn't work. Today I understood it better and ready many thanks friends
I tried to upload an image, but I could not.
Now i have version 210 :fingers-crossed:
Click to expand...
Click to collapse
Great, m8. And are you Google Certified? So i may update OP with info and link for firmware for those who want to update theor phones to v10.0.0.210.
Sent from my VOG-L29 using XDA Labs
SilviuO said:
Great, m8. And are you Google Certified? So i may update OP with info and link for firmware for those who want to update theor phones to v10.0.0.210.
Sent from my VOG-L29 using XDA Labs
Click to expand...
Click to collapse
does not appear certified or not certified. But in the Netflix search engine it does not appear, presumably it is not certified. Only not appear because the previous one was.
Thank you
Related
NOTE: I am currently extremely busy with work. Therefore, I can only irregularly participate here and updates will currently not be on a weekly basis. I will be looking for some support to see, if others can help with preparing new releases.
Dear all
This is a custom ROM for the Huami AmazFit Smartwatch (A1602) and the Xiaomi AmazFit PACE (A1612).
The ROM is fully functional, but may contain bugs.
FEATURES:
Based on Chinese firmware huanghe-1.2.51 stable firmware
additional translations:
- Italian (thanks to Nicola and @N3OMOD)
- Slovak (thanks to @jasterica and @rbt07(rbarat))
- Polish (thanks to @Kaudii)
- Czech (thanks to @zbani and @rbt07(rbarat))
- Spanish (thanks to @Alain and @saratoga)
- Russian (thanks to @silver-alx)
- French (Thanks to ericmo and Cyril)
- German (Thanks to Klaus H. and others)
- Hungarian (Thanks to gidano)
- Brazilian
- Basque (thanks to @iker)
- Hebrew (thanks to Uri and @1immortal)
additional fonts added
- Hebrew font (thanks to @itsay)
- Arabic fonts (thanks to @1immortal) -> re-added
- Tamil fonts (thanks to @madtech360)
- Thai fonts
- Khmer fonts (thanks to Piseth)
- updated fonts for Bidirectional language support with enable/disable function (see FAQ #14)
English voices in Sports app (thanks to @Fabien)
Updated tzdata (thanks to Alvaro)
command to change Bluetooth max volume to maximum (btVolBoost)
initd system to run customer script upon boot
new boot animation (thanks to @1immortal)
BETA (only for testing, maybe not working correctly):
- first Dutch translation (thanks to Ronny Gyles)
- Turkish (Thanks to ygecesefa )
- rootable with su pre-installed (call "root_amazfit" to enable or disable)
This release is based on the development firmware. We will need to see if it makes sense to follow the development series, as Huami seems to only target the Chinese market with this,
PERMANENT INSTALL:
Please find all information here: https://gitlab.com/Neuer_User/PACEfied_AmazFit/wikis/permanent-install
ATTENTION: You need to have an unlocked bootloader or run on a rooted ROM (such as PACEfied) for installing this ROM.
Community Project code:
The source code used to build the translated apps is available on the following GitLab repo:
https://gitlab.com/Neuer_User/PACEfied_AmazFit
If people want to contribute, log in, have a look around, download the files you want to translate, and send me the translated files, so I can include them.
Downloads:
Rel 39: Full install Version 1.2.51: (pulled because of problems, please use the below Update version)
Update from Rel 38 to Rel 39 (1.2.51): https://mega.nz/#!wc0DHTrI!08jLXgcDLqDkDF2GIPfQxD2uTJIefRG1WGdDgZQgrIA
Older versions:
Rel 38: Full install Version 1.2.50h: https://mega.nz/#!wUlwnLYR!4NhS_tTpakzCpSHDXKiVY34rqFR_slwXpK99QKo-OP8
Update from Rel 37 (1.2.49k) to Rel 38 (1.2.50h): https://mega.nz/#!oYESkbSQ!iLUGiqiTXKWYF6NVbtp8Y3pgrQT94Taz0keSZhwwGo8
Rel 37: Full install Version 1.2.49k: https://mega.nz/#!ZBEGWDxB!yKrjzI9EBzyiRPCZNgzP0q-kDLbQHC81iFTCw0sD-4w
Rel 36: Full install Version 1.2.49k: https://mega.nz/#!9ItxSITT!qGW2fY-fuv_RYVj77NXfyzjx7AOSl83K8y_zrde1ghE
Update from Rel 35 (1.2.48h) to Rel 36 (1.2.49k): https://mega.nz/#!wUcGFLLJ!Pv1Y4BPR1S4HCGfFXzVVunGRnGWcpNTYUYOC2WgGxlo
Rel 35: Full install Version 1.2.48h: https://mega.nz/#!YR8HwbxZ!DK3wV1lT...K!ouUYcONeynyqSzQe7Xx_2gdkXNEPEyN8HbrgTDyTgbE
Rel 33: Full install Version 1.2.47: https://mega.nz/#!hJUw3RpB!6LSm34TNyWPyW_jtxbCZzeGJQD4igwanC_t-sXFA_e4 (unreleased)
Rel 32: Full install Version 1.2.45: https://mega.nz/#!1dEnGDJS!Uv7hD-BThdaDNh2qEdwyQhTzyMRMjsCJ-UsyfVbQwa4
Rel 31: Full install Version 1.2.44: https://mega.nz/#!lQF0DDhb!VwVztDyJdYfxPZC7DmpGVAieDzErANK5aO4St1fuYtw (NOTE: sogoumap not translated in this release!)Rel 30: Full install Version 1.2.41: https://mega.nz/#!lM1ghCwZ!mKHbjGZSSisfETimtT2o9SYOx0Qa_LF9tae--mfUOQI
Rel 29: Full install Version 1.2.39: https://mega.nz/#!FNsyQIhZ!4jbbtfLfv4ZX8qBAtNcB0NPTrxr0ly7pgag8WnqJJs4
Rel 28: Full install Version 1.2.39: https://mega.nz/#!IAs2jAhJ!ngyMtxq_fcPnShNPsfILhra8vbeu4p4-Ut0MO3Fd4GE
Rel 27: Full install Version 1.2.37: https://mega.nz/#!cNUiQJDb!h2qPrfpU9sxGfu2P0JJNtbbpAblJS_FzR2aHp9Lvk44
Update from Rel 26 (1.2.35) to Rel 27 (1.2.37): https://mega.nz/#!5dciWITK!J3MMeYICcKJEYj2qw6KPOzEL9BjdIU9gattN6OVy17g
Rel 26: Full install Version 1.2.35: https://mega.nz/#!UdViVaBS!Fr3B9ECEm8muxQGv9lkOgGh6u40_LblPPaqiWgcE_Nc
Rel 25: Full install Version 1.2.32: https://mega.nz/#!IE8VVTiY!X82gsHbG988z8Kk22raqj_0Vy_tlgUe4or0CjU5SuE4
Rel 24: Full install Version 1.2.29: https://mega.nz/#!ZMcQya4T!9Cl6HU1WNThUONk4QsH8zBAaQizncqiHiPLZsTZ6Kvc
Update from Rel 22 (1.2.26a) to Rel 23 (1.2.27): https://mega.nz/#!AdcxhCiK!GtzvM5zcnxuNFW01Pr8R_DUafPDIR1EkASElnlb8KT8
Rel 23: Full install Version 1.2.27: https://mega.nz/#!dAsFQKhS!Z8Z9L0h9TW_EPy6SbqxUS3c8qNrhefg5rtzG2vSUjf0
Update from Rel 21 (1.2.25) to Rel 22 (1.2.26a): https://mega.nz/#!UJNEHRzA!tC9c3-Mi3xOdAZmgq34kzrqYBb5a5g7krh5ALWdazbc
Rel 22: Full install Version 1.2.26a: https://mega.nz/#!hUVGDQRT!g5SbkBeVPrgX-3DfUzecXA-NAnWYMsYhuWIwpoFHk6w
Update from Rel 20 (1.2.24) to Rel 21 (1.2.25): https://mega.nz/#!RFsBBL7Q!B3xov7FOMKjAi9jkR-UvfINOG_mwEv9-LwjAK4w0iFc
Rel 21: Full install Version 1.2.25: https://mega.nz/#!gIMC2LCC!8ZxFEe0dnCpqfbWwG5a2lC8_IT0wfEw4ccgOV4tiwkM
Rel 20: Full install Version 1.2.24: https://mega.nz/#!YMEA3bZB!76lg9PlvtRAsqBiAOec8ppAJ9xTtMQsTBJLsm0E_icU
Update from Rel 17 (1.2.21c) to Rel 18 (1.2.22): https://mega.nz/#!0ZlgkQ6R!SCx-XCte4sxSA3ws6G3PFyl-XRu63n3xmI7pBDFInVc
Rel 18: Full install Version 1.2.22: https://mega.nz/#!tE1jHSwY!88C4HgJwMLU3kX9pqDgQ2VA8QuVCyisLRvkxba0_57A
Update from Rel 16 (1.2.20) to Rel 17 (1.2.21c): https://mega.nz/#!oJciQTZa!7HjCTlavT8qvKzOCn6D9cX7U_wkFQYONFj2FKS17sUA
Rel 17: Full install Version 1.2.21c: https://mega.nz/#!hIEj2BCL!nEaosNn5VcQLs_7qMQAXAW566Ab5emv5HiJxwsa6tBg
Update from Rel 15 (1.2.19) to Rel 16 (1.2.20): https://mega.nz/#!9VNUXAbL!NtE2yh3nZfd486LGX-ulAv-APmMAwYY98EvLPgDRSSI
Rel 16: Full install Version 1.2.20: https://mega.nz/#!NA1lmajL!CI-R-o5zngN6vxcR20WpXa8vYGq-uk7T974mySmYvTA
Update from Rel 14 (1.2.18) to Rel 15 (1.2.19): https://mega.nz/#!JA8EXahK!mTJNaIHzSPAWKhk1pmCWGoaxbmv__OGiTdhtRKwAt-I
Rel 15: Full install Version 1.2.19: https://mega.nz/#!NV0xTBAY!fNj40JkFBpS-vE7L_EKcou9JS7wPS7WG_rHkKyOaaSk
Update from Rel 13 (1.2.17) to Rel 14 (1.2.18), permanent install: https://mega.nz/#!MNMUXLDT!Y1tpmG_IslYBR-VdvoQjKUJlHNGaJwFcMxix55FjigY
Rel 14: Full install Version 1.2.18, permanent install: https://mega.nz/#!wIUUXYAY!5rjrMiDMC8kV2JapHsaBR6EXJq7HInfR44IVk8HkZjYUpdate from Rel 12 (1.2.16) to Rel 13 (1.2.17), permanent install: https://mega.nz/#!VZcSGAqK!etek35aNnqKDa_h8ze5g2F3TAaVPr05Y0y4gy6uWm7M
Rel 13: Full install Version 1.2.17, permanent install: https://mega.nz/#!xB0FSTqY!SxB5PVtMB0rRLz7Jo46L9Ulj2LYHvu4F6T3P-NNvHmM
Update from Rel 11 (1.2.15d) to Rel 12 (1.2.16), permanent install: https://mega.nz/#!wR1yCCoa!rfg_DdCWz_z3F-V68XKjEbOiPgOoISIP8E7dYgts2Pk
Rel 12: Full install Version 1.2.16, permanent install: https://mega.nz/#!JNNh3Awb!_vMcgK8AGV6xm7Ns6Z8rkSd3te3T3OPCGXqp550mzcc
Update from Rel 10 (1.2.15a) to Rel 11 (1.2.15d), permanent install: https://mega.nz/#!9VVzEDJA!sZk7rFyrC9UDBG7pXpFTFSqL8Cx4lwc5vYtJ_FzxSbw
Rel 10: Full install Version 1.2.15a, permanent install: https://mega.nz/#!ZdMEiSzT!FYXbk_V4I5aigi2dSjL2UBOyBFMc3P4dRT4FkBXJHaw
Update from Rel 9 (1.2.14) to Rel 10 (1.2.15a), permanent install: https://mega.nz/#!cdVHTLAD!xguDxPPwp00K6VP_-So8Vgc9zCMw85doJgANdFbbwtM
Update from Rel 8 (1.2.13) to Rel 9 (1.2.14), permanent install: https://mega.nz/#!BE9DTJTb!h48h6kWAGRaY82-Xw_nMSPsHl4SUcQ9xJH-bhnbCfvs
Rel 9: Full install Version 1.2.14, permanent install: https://mega.nz/#!sMcSHbaY!fhsiKfeyK559328is4KoffNHpVaCX2PmQXuEYxnP32s
Update from Rel 7 (1.2.11c) to Rel 8 (1.2.13), permanent install: https://mega.nz/#!JZlgWDIB!il7-iekOIafLrQLPKZoMwbc0Yr8dT_NeAoukzAiME5Q
Rel 8: Full install Version 1.2.13, permanent install: https://mega.nz/#!IMUyRQxY!7ARUUNhA6UWhkzTEJAN9__P1dOqntZxC8UASf6wsU_Y
Update from Rel 6 (1.2.11) to Rel 7 (1.2.11c), permanent install: https://mega.nz/#!NYUHgbjL!jG0s6XynvtPW-w61UUBDCh0GY7EHyxNvvHCh3901KhU
Update from Rel 5 (1.2.10) to Rel 6 (1.2.11), permanent install: https://mega.nz/#!FB01gIJL!fRIvUALFjCaC7YGB_cxa3XFXF1DS5yZ-Q1iMZI_L5Og
Rel 6: Full install Version 1.2.11, permanent install: https://mega.nz/#!EZt1gTjK!znlhwdsS40N1DrbshWjM7floyiLlScjF3QFwRtGitxo
Rel 5: Full install Version 1.2.10, permanent install: https://www.google.com/url?q=https:...sntz=1&usg=AFQjCNG4Km1GaXmW0iY3hAcm6OEc9Czz2Q
Rel 5: Full install Version 1.2.10, temporary install: https://mega.nz/#!VVlykaLS!WiOPDP-dFbB_o_r49Q7YO-iSUnrzs3L8POgLcJhDqFE
Update from Rel 4 (1.2.9) to Rel 5 (1.2.10), permanent install: https://www.google.com/url?q=https:...sntz=1&usg=AFQjCNHTnJrNQ39QSLqJ_d5zUfmugw3XUA
Update from Rel 3 (1.2.8) to Rel 4 (1.2.9), permanent install: https://mega.nz/#!BdMCAbTJ!59vxmcKqSEqvCIKMYvLHteVE03xLb-oZCbc5PE5loEY
Rel 4: Full install Version 1.2.9, permanent install: https://mega.nz/#!gY0FhRiL!DLTnnuyy36KK8497zZ6jxW1k5KA9skTxpnfCxdhBWUs
Rel 3: Version 1.2.8, permanent install: https://mega.nz/#!lMExkATK!4ZOqX5GKJg_-GpGdPlMP0Q8igkpTAoQ1UpkWcxQZ0N4
Rel 3: Version 1.2.8, temporary install: https://mega.nz/#!UJkTwAbJ!HV57w7-x4kI99ix8SVmdp5RAXHtJ4n-w0WND26y8IhQ
Rel 2: Version 1.2.7, permanent install: https://mega.nz/#!wM9l1BxT!zauHlRWWQn2uqqZ-vvLzvfGvpTl6BleJOzkrtONzq10
Rel 1: Version 1.2.6c, temporary install: https://mega.nz/#!RB0wXK7T!h3DxA5ptWqwnfZzAON212D4BClgxNi3jp6HFPMFZaAw
Rel 1: Version 1.2.6c, permanent install: https://mega.nz/#!lU0SGbAJ!gaKB-sKboy-UfmzcqyLwB9OSnuzYnd7Bb6zDZ_xVOu0
Version 1.2.6b, temporary install: https://mega.nz/#!IEU11CiB!wU11MkyoZ051e5jl367meDmIswVBHtZ2kix90OnKK5Q
Pre-release version 1.2.5a, temporary install: https://mega.nz/#!kZchDS7b!PF0GP5ML_jLYt3FiG3ydet5q8mPzN_-wOHihbjKKh1I
Changelog of PACEfied releases:
Please find the latest changelog at the community page here: https://gitlab.com/Neuer_User/PACEfied_AmazFit/wikis/changelogs-for-pacefied-firmware-updates
Changelog of original Huami releases:
Please find the latest changelog at the community page here: https://gitlab.com/Neuer_User/PACEfied_AmazFit/wikis/changelogs-for-official-firmware-updates
FAQ:
The current FAQ can be found on the PACEfied community webpage:
https://gitlab.com/Neuer_User/PACEfied_AmazFit/wikis/home
If someone wants to help translate the new "TrainingPlan" app, have a look at the attached files, translate them and post the translation. I can then include this in the next releases.
How about already collected data on watch, will it be imported to the temporary rom and via verce?
Tomorrow will test
Inviato dal mio D6633 utilizzando Tapatalk
Neuer_User said:
If someone wants to help translate the new "TrainingPlan" app, have a look at the attached files, translate them and post the translation. I can then include this in the next releases.
Click to expand...
Click to collapse
I think in Facebook group that xml was already translated for Tomas's quests with translating the ROM!?
alexinc said:
How about already collected data on watch, will it be imported to the temporary rom and via verce?
Click to expand...
Click to collapse
If you come from the same firmware, then yes, for sure. If you are on another firmware (e.g. 1.2.3 or 1.3.0n) very likely (it did it always in my tests), but it is not guaranteed,
NOTE: This behaviour may change in the future. @silver-alx is using an approach to separate data partitions between the flashed FW on the watch and the temporary FW. This would be a requirement, if we start modding the code of the apps. So far, this is just FW 1.2.5a with english translation.
alexinc said:
I think in Facebook group that xml was already translated for Tomas's quests with translating the ROM!?
Click to expand...
Click to collapse
Great. If you can upload the translated xmls, I can include them in the next release.
Neuer_User said:
Great. If you can upload the translated xmls, I can include them in the next release.
Click to expand...
Click to collapse
I asked him to do so, as it's not my work and he should be the one to get the credits with Craig who did the translation!
A big thanks, great!!
The process "push the system image and the md5s onto the sdcard" about how many minutes will the process take?
I`m been waiting for 10 minutes.
I found out, about 350 seconds.
translated what i could with Google translate,bing and bab.la.
if someone knows Chinese, please complete the not-translated ones, or i'll update the files tomorrow, hopefully will have access to a person who knows Chinese.
1immortal said:
translated what i could with Google translate,bing and bab.la.
if someone knows Chinese, please complete the not-translated ones, or i'll update the files tomorrow, hopefully will have access to a person who knows Chinese.
Click to expand...
Click to collapse
We have with Craig helping out on Facebook group!
oh, ok, he'll probably do a better job than all of these machine translations
1immortal said:
translated what i could with Google translate,bing and bab.la.
if someone knows Chinese, please complete the not-translated ones, or i'll update the files tomorrow, hopefully will have access to a person who knows Chinese.
Click to expand...
Click to collapse
I don't speak chinese but i looked over the arrays.xml and it says "Difficulty" twice with different chinese words.
English translation gave me "Difficult" and "Difficulty".
I tried to translate to German where it says "schwierig" and "Kleine Schwierigkeit" which makes more sense as it means "Difficult" and "low Difficulty"
I think Difficult and Easy would be the correct translation.
"Cancellation" and "Its too much!" seem to be a bit odd, too but for further translation one should know what the function does on the watch. Unfortunately i am still waiting for mine....
Version2 as translated by Craig over at Facebook. Due to lack of account here he gave me permission to share. So it's not my work, just uploading...
Neuer_User said:
If someone wants to help translate the new "TrainingPlan" app, have a look at the attached files, translate them and post the translation. I can then include this in the next releases.
Click to expand...
Click to collapse
Hi my friend,
It is already done. You can find it in FB group (Xiaomi Huami Amazfit Pace Smartwach) in files train_plan_en.zip or I can send it to you in 2 hours.
There are few more files which you need to copy to assets directory and subdirecrories en and cn (en sub doesnt work so I copied to both).
EDIT: I see somebody already copy this file. There is also TraininPlanEn-v1.zip which including translated apk. You can maybe use it.
kkti said:
Hi my friend,
It is already done. You can find it in FB group (Xiaomi Huami Amazfit Pace Smartwach) in files train_plan_en.zip or I can send it to you in 2 hours.
There are few more files which you need to copy to assets directory and subdirecrories en and cn (en sub doesnt work so I copied to both).
EDIT: I see somebody already copy this file. There is also TraininPlanEn-v1.zip which including translated apk. You can maybe use it.
Click to expand...
Click to collapse
Thanks, guys. Very good.
Do you have all your work at an open central place, e.g. github, or gitlab? I'd like to have an open community project, where many people can help translate or mod the firmware. In case, you do not have that yet, I would like to create such a project.
Neuer_User said:
Thanks, guys. Very good.
Do you have all your work at an open central place, e.g. github, or gitlab? I'd like to have an open community project, where many people can help translate or mod the firmware. In case, you do not have that yet, I would like to create such a project.
Click to expand...
Click to collapse
It is great idea. There is not such a central place. So if you create one it would be great.
Another idea. After friday OTA update you need to prepare new version based on last version. I think we as community can help you with something if you want. I don't know how you check differences between version I mean apks? But we can just decrypt apk and check string.xml and array.xml for changes and than create new apk based on last version.
I already know the process I prepared english version for WearHealth.apk and TraningPlan.apk as well. Both are working very well.
But maybe you require your own process for modification.
Thanks for great work
kkti said:
It is great idea. There is not such a central place. So if you create one it would be great.
Another idea. After friday OTA update you need to prepare new version based on last version. I think we as community can help you with something if you want. I don't know how you check differences between version I mean apks? But we can just decrypt apk and check string.xml and array.xml for changes and than create new apk based on last version.
I already know the process I prepared english version for WearHealth.apk and TraningPlan.apk as well. Both are working very well.
But maybe you require your own process for modification.
Thanks for great work
Click to expand...
Click to collapse
Thanks, any help is greatly appreciated.
I will try to setup a good structure, so that people can easily participate and help. This will, however, take a little bit of time.
Btw. have you tried the PACEfied ROM yet? It has all applications translated to English (except TrainingPlan, which I will add in the next release.
Returning to oreo GUIDE
We are going to speak about Returning to oreo for Samsung J4 PLUS .
Requirements
- Any archive decompress tool .
WINDOWS : Winrar & 7zip .
LINUX : U can use shell or any archive decompress tool .
ANDROID : Zarchiver .
- Custom recovery .
- LZ4 Tool .
WINDOWS : Here .
LINUX : Package name is liblz4-tool .
ANDROID : Use termux app , pkg update ; pkg install lz4 .
- Oreo stock rom .
Code:
U CAN'T FIND IT FREE ON MOST SITES OR IT WAS DELETED FROM OTHER SITES .
BUT I FOUND THIS SITE PROVIDES STOCK ROM FOR FREE AND WITHOUT SIGN IN , BUT DOWNLOADING SPEED IS SLOW :
[URL="https://samfrew.com/"][COLOR="Red"]SITE LINK[/COLOR][/URL] .
- Patience .
Lets start steps
A - Preparing . . .
Download oreo stock rom .
Unzip stock rom zip .
Rename AP ( tar.md5 to tar ) .
Decompress AP ( system - boot - vendor) & CSC ( odm only ) tar files in a dir (eg work) . ( WINDOWS : 7ZIP )
Decompress lz4.zip in previous dir ( WINDOWS ONLY)
Open cmd ( WINDOWS ) or console ( LINUX ) or termux ( ANDROID , but if u face issue try to move files to termux home dir using com.android.documentsui app , it is in any android system ) in previous dir .
Open as root or administrator write this :
Code:
- lz4 -d system.img.ext4.lz4 --no-sparse . ( [COLOR="red"]WINDOWS : lz4.exe [/COLOR])
Then delete system lz4 compressed file .
- lz4 -d -m *.lz4
Then delete all lz4 compressed file .
Rename all img.ext4 to img .
Copy all ( system - vendor - boot - odm ) img to your phone .
B - Installing . . .
- Reboot recovery
- Wipe data , system , vendor .
- From custom recovery teriminal or adb shell , go to img saved location ( using cd command ) :
Code:
- simg2img odm.img odm.raw
- dd if=odm.raw of=/dev/block/bootdevice/by-name/odm
- Install system .
Notice : With twrp , Better to reboot recovery .
- Install boot , vendor .
- Install custom kernel . (if u want)
- Install security disable stuff :
J6+ J4+ disable encryption : here .
Disable all pie security : here .
- Install magisk .
C - Waiting until it boot . . .
- Done phone booted . :good:
Thanks
• @ashyx for Twrp & J6+ J4+ disable encryption .
• @SebaUbuntu for custom recoveries .
• me for writing this thread .
• @topjohnwu for magisk .
Indonesia region try this mirror https://drive.google.com/file/d/1lGxg2R5HJiBRWvNy1uMBKd-RJ56u49Gt/view
Credit nanda.id
Can I lock the bootloader after this?
btw thanks so much for this guide, I've always wanted to downgrade...
this phone has been flashed with unauthorized software, meh.
If you're running Pie, stay there and be happy.
blackhawk said:
If you're running Pie, stay there and be happy.
Click to expand...
Click to collapse
my touchscreen didn't work after updating to the latest one
How to fix this phone has been flashed with unauthorized software
i have not working face and fingerprint unlock..
nick D1256 said:
i have not working face and fingerprint unlock..
Click to expand...
Click to collapse
i cant register it
zawarud0 said:
this phone has been flashed with unauthorized software, meh.
Click to expand...
Click to collapse
Install medusa Kernel
Hello. I have J6+ and followed all the steps carefully but I have the problem of
"your device has been flashed with unauthorized firmware and is locked"
what can I do? I really want an Android 8 or 8.1 custom ROM
Hi all,
Just would like to share some cust and preload files needed for updating to EMUI 11. I don't think these firmwares are available on Firmaware Finder.
Code:
ELS-N39-PRELOAD 11.0.0.3(C432R3)
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v464313/f1/full/changelog_preload_hw_eu_R3.xml
Code:
ELS-N39-CUST 11.0.0.3(C432)
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v464311/f1/full/changelog_cust_hw_eu.xml
How I find these:
I wrote a python scraper which goes through all urls like:
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v{version_number}/f1/full/changelog_preload_hw_eu_R3.xml
Click to expand...
Click to collapse
where version_number is from 400000, 510000
the file name part "/changelog_preload_hw_eu_R3.xml" makes sure all paths found are for C432(eu) and R3.
Land on a OTA - updatable firmware
I used the following OS firmare:
Code:
ELS-LGRP6-OVS 11.0.0.151
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v492669/f1/full//update_full_base.zip
After which, I got an OTA update to 11.0.0.168
This can solve the problem many people are having: Not getting updates after downgrade.
This working.....juhuhu....thanks!
Usually when you can't get OTA is because oeminfo is broken (Broken as in it has the wrong strings in it). I had to manually edit mine to get OTA back.
But if it works it's good for you.
realseangao said:
I wrote a python scraper which goes through all urls like:
where version_number is from 400000, 510000
the file name part "/changelog_preload_hw_eu_R3.xml" makes sure all paths found are for C432(eu) and R3.
Click to expand...
Click to collapse
Share script
oslo83 said:
Share script
Click to expand...
Click to collapse
This is in python3, I made use of aiohttp to boost the speed. You might want to pip install aiohttp before hand.
Python:
import asyncio
import aiohttp
from time import sleep
cust_template = "http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v{}/f1/full/changelog_cust_hw_eu.xml"
preload_template = "http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v{}/f1/full/changelog_preload_hw_eu_R3.xml"
async def get(i):
url = cust_template.format(i)
try:
async with aiohttp.ClientSession() as session:
async with session.get(url=url) as response:
if (response.status == 200):
print("Found: {}".format(i))
return i
else:
print('Checked: {}, Status Code: {}'.format(url, response.status))
except Exception as e:
print("Unable to get url {} due to {}.".format(url, e.__class__))
return None
async def main(start, end):
ret = await asyncio.gather(*[get(i) for i in range(start, end)])
filtered = list(filter(None, ret))
print("Finalized batch. ret is a list of: {}".format(filtered))
return filtered
res = []
for i in range(460000, 470000, 1000):
print("Start new round: {}".format(i))
res.extend(asyncio.run(main(i, i + 1000)))
print("Ending round: {}".format(res))
# The server has DDOS protection
sleep(5)
print('Final versions found: {}'.format(res))
ante0 said:
Usually when you can't get OTA is because oeminfo is broken (Broken as in it has the wrong strings in it). I had to manually edit mine to get OTA back.
But if it works it's good for you.
Click to expand...
Click to collapse
The reason my OTA was not working was that I landed on a version that has never been officially pushed out from Huawei onto P40 pro plus but shows up in Firmware Finder (I was on 10.1.0.182 before).
I am assuming when pushing updates Huawei server checks your OS version info to determine your next update:
As a made-up example:
If you are on 11.0.151, it will give you 11.0.168
If you are on 11.0.152, server does not know which version to give you since in Huawei's database, you should not land on 11.0.152.
Just as data points:
ELS-LGRP6-OVS 11.0.0.168 and 11.0.0.151 are both official versions for my ELS-N39 (C432)
realseangao said:
Hi all,
Just would like to share some cust and preload files needed for updating to EMUI 11. I don't think these firmwares are available on Firmaware Finder.
Click to expand...
Click to collapse
Hi,
Thanks for sharing this with us, I tried it and it worked flawless, I even got the OTA updates back and updated to 11.0.0.168
Excellent job mate
Really THANK YOU !
Now i'm back on EMUI 11 !
realseangao said:
Hi all,
Just would like to share some cust and preload files needed for updating to EMUI 11. I don't think these firmwares are available on Firmaware Finder.
Code:
ELS-N39-PRELOAD 11.0.0.3(C432R3)
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v464313/f1/full/changelog_preload_hw_eu_R3.xml
Code:
ELS-N39-CUST 11.0.0.3(C432)
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v464311/f1/full/changelog_cust_hw_eu.xml
How I find these:
I wrote a python scraper which goes through all urls like:
where version_number is from 400000, 510000
the file name part "/changelog_preload_hw_eu_R3.xml" makes sure all paths found are for C432(eu) and R3.
Land on a OTA - updatable firmware
I used the following OS firmare:
Code:
ELS-LGRP6-OVS 11.0.0.151
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v492669/f1/full//update_full_base.zip
After which, I got an OTA update to 11.0.0.168
This can solve the problem many people are having: Not getting updates after downgrade.
Click to expand...
Click to collapse
I don't know that this is right.
And if you don't mind Please suggest me to relock bootloader.
hi all, i'm on 10.1.0.137(C636E3R1P1). I tried to find firmware package URL from Firmware Finder but found that 10.1.0.175 and the rest of the firmware are not available anymore. Error: The remote server returned an error: (404) Not Found.
Can anyone help to provide the package URL so that I can upgrade my firmware from 10.1.0.137 to 10.1.0.175 then to 11.0.0.151?
realseangao said:
Hi all,
Just would like to share some cust and preload files needed for updating to EMUI 11. I don't think these firmwares are available on Firmaware Finder.
Snip...
Click to expand...
Click to collapse
That's a really useful post and thank you for the Python script to help us do it for ourselves. I think I am a little late as it seems 'something has changed'
Following the links in my browser, I am receiving the not very useful page 'error' from any of the links posted for http://update.dbankcdn.com/
In addition, the Python script is returning (a lot of) 404's:
Checked: http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v460009/f1/full/changelog_cust_hw_eu.xml, Status Code: 404
Checked: http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v460029/f1/full/changelog_cust_hw_eu.xml, Status Code: 404
Checked: http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v460008/f1/full/changelog_cust_hw_eu.xml, Status Code: 404
... snip ... etc.,
I'd be very grateful if someone can help find an OTA updateable EMUI 11 firmware please. I am currently (stuck) on 10.1.0.145 (C432E2R3P3). If it's something as straightforward as a tweak to the URL's in the script, then great and thanks in advance.
I am aware of available firmware here, but 11.0.0.5 looks pretty old in comparison to 11.0.0.168 - and it's not clear whether I'd be able to update with OTA after installing that firmware.
realseangao said:
Hi all,
Just would like to share some cust and preload files needed for updating to EMUI 11. I don't think these firmwares are available on Firmaware Finder.
Code:
ELS-N39-PRELOAD 11.0.0.3(C432R3)
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v464313/f1/full/changelog_preload_hw_eu_R3.xml
Code:
ELS-N39-CUST 11.0.0.3(C432)
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v464311/f1/full/changelog_cust_hw_eu.xml
How I find these:
I wrote a python scraper which goes through all urls like:
where version_number is from 400000, 510000
the file name part "/changelog_preload_hw_eu_R3.xml" makes sure all paths found are for C432(eu) and R3.
Land on a OTA - updatable firmware
I used the following OS firmare:
Code:
ELS-LGRP6-OVS 11.0.0.151
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v492669/f1/full//update_full_base.zip
After which, I got an OTA update to 11.0.0.168
This can solve the problem many people are having: Not getting updates after downgrade.
Click to expand...
Click to collapse
AndroidKittyCat said:
That's a really useful post and thank you for the Python script to help us do it for ourselves. I think I am a little late as it seems 'something has changed'
Following the links in my browser, I am receiving the not very useful page 'error' from any of the links posted for http://update.dbankcdn.com/
In addition, the Python script is returning (a lot of) 404's:
Checked: http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v460009/f1/full/changelog_cust_hw_eu.xml, Status Code: 404
Checked: http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v460029/f1/full/changelog_cust_hw_eu.xml, Status Code: 404
Checked: http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v460008/f1/full/changelog_cust_hw_eu.xml, Status Code: 404
... snip ... etc.,
I'd be very grateful if someone can help find an OTA updateable EMUI 11 firmware please. I am currently (stuck) on 10.1.0.145 (C432E2R3P3). If it's something as straightforward as a tweak to the URL's in the script, then great and thanks in advance.
I am aware of available firmware here, but 11.0.0.5 looks pretty old in comparison to 11.0.0.168 - and it's not clear whether I'd be able to update with OTA after installing that firmware.
Click to expand...
Click to collapse
realseangao said:
Hi all,
Just would like to share some cust and preload files needed for updating to EMUI 11. I don't think these firmwares are available on Firmaware Finder.
Code:
ELS-N39-PRELOAD 11.0.0.3(C432R3)
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v464313/f1/full/changelog_preload_hw_eu_R3.xml
Code:
ELS-N39-CUST 11.0.0.3(C432)
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v464311/f1/full/changelog_cust_hw_eu.xml
How I find these:
I wrote a python scraper which goes through all urls like:
where version_number is from 400000, 510000
the file name part "/changelog_preload_hw_eu_R3.xml" makes sure all paths found are for C432(eu) and R3.
Land on a OTA - updatable firmware
I used the following OS firmare:
Code:
ELS-LGRP6-OVS 11.0.0.151
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v492669/f1/full//update_full_base.zip
After which, I got an OTA update to 11.0.0.168
This can solve the problem many people are having: Not getting updates after downgrade.
Click to expand...
Click to collapse
Hi. I'm having issues with my phone and I was searching for ways to sort it out. I came across this but seems like the links are unavailable. Do you perhaps have another download link? For the cust files, preload file and Ota?
Link geht leider nicht mehr.
could you help us with some links i do have the same problem
I received a lot of help in this thread, which enabled me to upgrade my P40 Pro + after getting GMS working.
I hope it helps.
Easy to way to install a GSI on your Samsung A21s without installing a Virtual Linux.
NFC, Screen Cast, and USB MTP unfortunately is not working with AOSP 10 and 11. Backup all your data.
If don't want to make one, download my Pre-Rooted GSIs below and flash.
*Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Android 10 -> Download (MediaFire)Android 11 -> Download (MediaFire)Android 11 - AOSP 11.0 v306 -> Download (MEGA) - NEWAndroid 10 Screenshots
1. Requirements:
1. Unlock your Bootloader2. Download and Install a Linux Subsystem -> Ubuntu Subsystem -> "Tutorial How to install Linux Subsystem on Windows 10 | or search how to"3. GSI Android 10 A/B Gapps -> Download only the "arm64, A/B". I recommend releases from Treble Experimentations AOSP like "system-roar-arm64-ab-gapps.img.xz". 4. Samsung.zip -> There's all needed tools and files - Odin, 7-Zip ZS etc...
- Download Samsung.zip and extract the folder "Samsung" to your desktop, and extract your chosen GSI using to this folder.
- Download your stock firmware and extract the super.img.lz4 file from AP_A217XXXXXXXXXX_XXX_XXXX_REV00_XXX.tar.md5 with 7-Zip ZS.
- Now extract super.img.lz4 using 7-Zip ZS (don't use 7-zip) to Samsung folder. Rename super.img to stock_super.img.
2. Convert stock_super.img to raw_super.img:Open CMD ad use this codes:
cd C:\Users\%USERNAME%\Desktop\Samsungsimg2img.exe stock_super.img raw_super.img
Wait...
3. Extract raw_super.img:On your Samsung folder, use SHIFT key of your keyboard + right click and click at "Open Linux Shell Here", wait a little, and use this code and wait the extraction:
./lpunpack --slot=0 raw_super.img
*If the extraction is completed, verify if there's this files odm.img, system.img, vendor.img and product.img. Delete or rename system.img and product.img, then extract your GSI to Samsung folder and rename the xxx.img file to system.img.
4. Pack all the files and Flash:No math here! Just use this code on Terminal and wait (Ignore errors like "Partition system, vendor, odm will resize..." or "Invalid sparce file format at header magic...")
./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:5557452800 --group main:3819597824 --partition system:readonly:3340271616:main --image system=./system.img --partition vendor:readonly:474976256:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
Wait....
Use 7-Zip to archive the super.img to .tar (super.tar) and flash it on Odin (AP) and wait the phone to boot.
Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Notes:I not responsible for any damage on your phone. If anything occurs, just flash your stock regional firmware through Odin.
If this tutorial did not work, you did something wrong or your phone is not supported. Don't forget to wipe your data through Recovery, it's very important.
If you want Magisk working on your A21s I recommend you to report to an issue Topjohnwu at Github.
Dear Wer99,
I Successfully Made A Non-Rooted GSI By Following Your [Tutorial / Guide],
I'm Wondering How Could I Add SuperSU & Root Permission In It
GSI : [CherishOS, AOSP10, AOSP11]
Wer99 said:
Easy to way to install a GSI on your Samsung A21s without installing a Virtual Linux.
NFC, Screen Cast, and USB MTP unfortunately is not working with AOSP 10 and 11. Backup all your data.
If don't want to make one, download my Pre-Rooted GSIs below and flash.
*Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Android 10 -> Download (MediaFire)Android 11 -> Download (MediaFire)Android 11 - AOSP 11.0 v306 -> Download (MEGA) - NEWAndroid 10 Screenshots
1. Requirements:
1. Unlock your Bootloader2. Download and Install a Linux Subsystem -> Ubuntu Subsystem -> "Tutorial How to install Linux Subsystem on Windows 10 | or search how to"3. GSI Android 10 A/B Gapps -> Download only the "arm64, A/B". I recommend releases from Treble Experimentations AOSP like "system-roar-arm64-ab-gapps.img.xz". 4. Samsung.zip -> There's all needed tools and files - Odin, 7-Zip ZS etc...
- Download Samsung.zip and extract the folder "Samsung" to your desktop, and extract your chosen GSI using to this folder.
- Download your stock firmware and extract the super.img.lz4 file from AP_A217XXXXXXXXXX_XXX_XXXX_REV00_XXX.tar.md5 with 7-Zip ZS.
- Now extract super.img.lz4 using 7-Zip ZS (don't use 7-zip) to Samsung folder. Rename super.img to stock_super.img.
2. Convert stock_super.img to raw_super.img:Open CMD ad use this codes:
cd C:\Users\%USERNAME%\Desktop\Samsungsimg2img.exe stock_super.img raw_super.img
Wait...
3. Extract raw_super.img:On your Samsung folder, use SHIFT key of your keyboard + right click and click at "Open Linux Shell Here", wait a little, and use this code and wait the extraction:
./lpunpack --slot=0 raw_super.img
*If the extraction is completed, verify if there's this files odm.img, system.img, vendor.img and product.img. Delete or rename system.img and product.img, then extract your GSI to Samsung folder and rename the xxx.img file to system.img.
4. Pack all the files and Flash:No math here! Just use this code on Terminal and wait (Ignore errors like "Partition system, vendor, odm will resize..." or "Invalid sparce file format at header magic...")
./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:5557452800 --group main:3819597824 --partition system:readonly:3340271616:main --image system=./system.img --partition vendor:readonly:474976256:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
Wait....
Use 7-Zip to archive the super.img to .tar (super.tar) and flash it on Odin (AP) and wait the phone to boot.
Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Notes:I not responsible for any damage on your phone. If anything occurs, just flash your stock regional firmware through Odin.
If this tutorial did not work, you did something wrong or your phone is not supported. Don't forget to wipe your data through Recovery, it's very important.
If you want Magisk working on your A21s I recommend you to report to an issue Topjohnwu at Github.
Click to expand...
Click to collapse
I tried all of this and I even went as far as trying to literally change the filesystem UUID and the filesystem of system.img as well, I detected some issues when booting a GSI and it's that the filesystem and the filesystem UUID's had to match (filesystem had to be EXT2 for some reason), and after I did all of that, I flashed the super.img to my phone but after a few seconds of it trying to boot (10 seconds after it's past the unlocked bootloader screen) it just reboots and kicks me to fastboot mode, a friend of mine told me that if it booted to fastboot it meant that the bootloader was able to pass instructions to the OS but failed, hence why it kicked me to fastboot, and after that I tried with different GSIs and neither of them worked sadly.
Also in the attributes I'd recommend changing "readonly" to "none" so that the partitions are Read/Write from super.img, after flashing super.img, just edit the fstab file (located in "/etc/fstab" for recovery) and replace "ro" in the mount points with "rw" so that you can read and write data to them, the point of this is to make the partitions read and write so that you can edit them and install anything you'd like, and that's exactly the reason I did it.
After some time we got a modded magisk apk that does work and doesn't have the legacy device detection issue that it had before, due to the phone using dynamic partitions and using a ramdisk, Magisk would detect the device as legacy and it would use "SAR_init", something that the device doesn't needs and because the boot process fails, it reboots.
Also, before I realized that you could make the partitions inside super.img read/write, I would usually use readonly and it wouldn't work either, I'd appreciate if you could help me with this.
Wer99 said:
Easy to way to install a GSI on your Samsung A21s without installing a Virtual Linux.
NFC, Screen Cast, and USB MTP unfortunately is not working with AOSP 10 and 11. Backup all your data.
If don't want to make one, download my Pre-Rooted GSIs below and flash.
*Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Android 10 -> Download (MediaFire)Android 11 -> Download (MediaFire)Android 11 - AOSP 11.0 v306 -> Download (MEGA) - NEWAndroid 10 Screenshots
1. Requirements:
1. Unlock your Bootloader2. Download and Install a Linux Subsystem -> Ubuntu Subsystem -> "Tutorial How to install Linux Subsystem on Windows 10 | or search how to"3. GSI Android 10 A/B Gapps -> Download only the "arm64, A/B". I recommend releases from Treble Experimentations AOSP like "system-roar-arm64-ab-gapps.img.xz". 4. Samsung.zip -> There's all needed tools and files - Odin, 7-Zip ZS etc...
- Download Samsung.zip and extract the folder "Samsung" to your desktop, and extract your chosen GSI using to this folder.
- Download your stock firmware and extract the super.img.lz4 file from AP_A217XXXXXXXXXX_XXX_XXXX_REV00_XXX.tar.md5 with 7-Zip ZS.
- Now extract super.img.lz4 using 7-Zip ZS (don't use 7-zip) to Samsung folder. Rename super.img to stock_super.img.
2. Convert stock_super.img to raw_super.img:Open CMD ad use this codes:
cd C:\Users\%USERNAME%\Desktop\Samsungsimg2img.exe stock_super.img raw_super.img
Wait...
3. Extract raw_super.img:On your Samsung folder, use SHIFT key of your keyboard + right click and click at "Open Linux Shell Here", wait a little, and use this code and wait the extraction:
./lpunpack --slot=0 raw_super.img
*If the extraction is completed, verify if there's this files odm.img, system.img, vendor.img and product.img. Delete or rename system.img and product.img, then extract your GSI to Samsung folder and rename the xxx.img file to system.img.
4. Pack all the files and Flash:No math here! Just use this code on Terminal and wait (Ignore errors like "Partition system, vendor, odm will resize..." or "Invalid sparce file format at header magic...")
./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:5557452800 --group main:3819597824 --partition system:readonly:3340271616:main --image system=./system.img --partition vendor:readonly:474976256:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
Wait....
Use 7-Zip to archive the super.img to .tar (super.tar) and flash it on Odin (AP) and wait the phone to boot.
Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Notes:I not responsible for any damage on your phone. If anything occurs, just flash your stock regional firmware through Odin.
If this tutorial did not work, you did something wrong or your phone is not supported. Don't forget to wipe your data through Recovery, it's very important.
If you want Magisk working on your A21s I recommend you to report to an issue Topjohnwu at Github.
Click to expand...
Click to collapse
Also, Just so you know, the recovery that we have is OrangeFox R11 which is currently an alpha build, thanks to magisk I was able to use the tool "dd" in termux to flash the recovery.img to /dev/block/by-name/recovery (aka the recovery partition) and this helped me bypass DL mode which is even worse now that I upgraded to U5 (I regret it and I tried downgrading from recovery instead of DL mode but the linux kernel itself protects the mmcblk0boot0 partition which is supposed to be the partition where the "BL" is located, and I tried flashing the sboot.bin file to that partition and it didn't work due to it being protected
Anyways back to the original topic, I don't know how but after flashing OrangeFox R11 with dd in android (I used su with magisk of course because), OrangeFox managed to boot with stock vbmeta and this build was supposedly built with A10's firmware in mind, not A11's firmware, so I have some hopes that flashing super.img from recovery might work if given the right vendor and firmware, I even flashed a vbmeta that was made for U3 from OrangeFox and it booted without any issues, oddly enough OneUI booted with that U3 vbmeta.img
LonelyCracker said:
Dear Wer99,
I Successfully Made A Non-Rooted GSI By Following Your [Tutorial / Guide],
I'm Wondering How Could I Add SuperSU & Root Permission In It
GSI : [CherishOS, AOSP10, AOSP11]
Click to expand...
Click to collapse
You don't need SuperSU anymore, There's already a fixed magisk for it, Here's the links:
[SHARING] HOW TO ROOT A21S STOCK ROM WITH MAGISK
Hello friends I just want to share how to root A21S stock rom in case anybody needs it: 1. Unlock bootloader 2. (On PC) Extract boot.img.lz4 from AP...tar file, then copy it to phone 3. (On phone) Install ZArchiver to extract boot.img from...
forum.xda-developers.com
[ROOT] Modified Magisk for Galaxy A21S (R)
It seems that the A21S hasn't had any root since it was released (other than pre-rooted GSI ROMS) When flashing Magisk, the phone went into bootloop, and the only way to fix it was to flash stock rom via Odin. After some analysis, it seems that...
forum.xda-developers.com
David112+ said:
You don't need SuperSU anymore, There's already a fixed magisk for it, Here's the links:
[SHARING] HOW TO ROOT A21S STOCK ROM WITH MAGISK
Hello friends I just want to share how to root A21S stock rom in case anybody needs it: 1. Unlock bootloader 2. (On PC) Extract boot.img.lz4 from AP...tar file, then copy it to phone 3. (On phone) Install ZArchiver to extract boot.img from...
forum.xda-developers.com
[ROOT] Modified Magisk for Galaxy A21S (R)
It seems that the A21S hasn't had any root since it was released (other than pre-rooted GSI ROMS) When flashing Magisk, the phone went into bootloop, and the only way to fix it was to flash stock rom via Odin. After some analysis, it seems that...
forum.xda-developers.com
Click to expand...
Click to collapse
Yeah I Know But I'm Just Interested In Making A Prerooted GSI
LonelyCracker said:
Yeah I Know But I'm Just Interested In Making A Prerooted GSI
Click to expand...
Click to collapse
What's the point of making a prerooted GSI with an outdated root method?
You can't even install modules with SuperSU
To David112+ :
In My Opinion, Prerooted GSI Is Way Better.
You Could See The Comparison I Made Here.
Also Making One GSI Could Gain Me Lots Of Experience.
So I Couldn't Think Of The Reason Why Not
Magisk Patched Stock [Firmware / ROM] Also Have It Own Problem,
Which You Could Find Here.
LonelyCracker said:
To David112+ :
In My Opinion, Prerooted GSI Is Way Better.
You Could See The Comparison I Made Here.
Also Making One GSI Could Gain Me Lots Of Experience.
So I Couldn't Think Of The Reason Why Not
Magisk Patched Stock [Firmware / ROM] Also Have It Own Problem,
Which You Could Find Here.
Click to expand...
Click to collapse
I don't think you've realized or checked the group of the phone but a load of people have already rooted their ROMs with Magisk and so far they have no problems, and still, everyone agrees that installing modules somewhere from the internet is the responsibility of the end user.
And I'm pretty sure that everyone agrees that magisk is the best root method, and even if you wipe data, you can just reinstall the Magisk apk to get the root prompt and finish setting it up, or better yet. use the systemizer module to systemize the magisk apk so that it's installed in system instead of data.
Making a prerooted GSI is just a waste of time, I'd rather just make normal GSI that's flashable on the phone and just install Magisk or systemize the Magisk APK.
I do agree that making a GSI flashable for the phone makes you gain a lot of experience but you're wasting your time into something that barely anyone is going to use, due to the fact that it has SuperSU which is old and outdated and most people prefer Magisk anyways because it's updated and not only that but you can pretty much install anything you'd like with the modules.
To David112+ :
Sorry To Disagree With You, I Was Trying To Acheive A Goal There .
My Goal Was To Get ADB (Android Debug Bridge) With "adb root" Working On Magisk Patched Stock [Firmware / ROM]. After Many Research & Attempt To Acheive That, I Gave Up... I Gained Some Knowledge There Too. I Know That Stock Rom Are For Production Purpose & I Can't Gain Root Access Using ADB (Android Debug Bridge).
Hopefully I Could Get Help Somewhere.
But Fun Fact Is...
I Water-Damaged My Phone
Question :
1.) Is It Possible To Make A Non Rooted GSI & Patch It With Magisk ? How ?
LonelyCracker said:
To David112+ :
Sorry To Disagree With You, I Was Trying To Acheive A Goal There .
My Goal Was To Get ADB (Android Debug Bridge) With "adb root" Working On Magisk Patched Stock [Firmware / ROM]. After Many Research & Attempt To Acheive That, I Gave Up... I Gained Some Knowledge There Too. I Know That Stock Rom Are For Production Purpose & I Can't Gain Root Access Using ADB (Android Debug Bridge).
Hopefully I Could Get Help Somewhere.
But Fun Fact Is...
I Water-Damaged My Phone
Question :
1.) Is It Possible To Make A Non Rooted GSI & Patch It With Magisk ? How ?
Click to expand...
Click to collapse
Custom ROMs should work with ADB root normally
2. To install Magisk just use the links that I shared in this post (https://forum.xda-developers.com/t/...d-gsis-for-samsung-a21s.4269227/post-84975373)
After upgrading to U5, I can't install these GSIs anymore. It bootloop all the times
To David112+ :
But Is Not Possible To Use ADB (Android Debug Bridge) On Magisk Patched Stock [Firmware / ROM]. What I Was Saying Is To Use "adb root" On Magisk Patched Stock [Firmware / ROM]
I'm Only Able To Use The Command "adb root" In Custom GSI Built By Wer99.
Not Every Custom Build GSI Are Prerooted.
Maybe You're Right Magisk Is Better Than Old Little SuperSU. But I Need "adb root" To Work With It
thatha said:
After upgrading to U5, I can't install these GSIs anymore. It bootloop all the times
Click to expand...
Click to collapse
If you have magisk with stock ROM, good news for you, I'll be working a guide in how to get a GSI installed as a magisk module, I tested this with ShapeShiftOS and I got as far as the boot animation of ShapeShiftOS, Once I was booted I checked ADB and sdcard was encrpyted and that's why it wasn't able to start correctly, it was just stuck in the google logo with a loading bar, I'm gonna try decrypting data, formatting and then installing the module
If this does work then I'll be releasing a guide in how to get a GSI of your preference working as a magisk module
Explanation: Thanks to Magisk's Magic Mount feature, I'm able to systemlessly swap the assets of OneUI with a Custom ROM's of my choosing, such as ShapeShiftOS
Edit: This idea is discarded, Because of the userdata partition being encrypted I can't use ShapeShiftOS, and even after decrypting I can't use it because OneUI gets stuck in "Starting android" when using the boot image with patched fstab and magisk
And if I download gsi android 11 through mediafire, will I have to do all this procedure? or just flash on odin? A21S ANDROID 11.
To Oroki:
These GSI Is Ready To Be Flashed.
LonelyCracker said:
To Oroki:
These GSI Is Ready To Be Flashed.
Click to expand...
Click to collapse
but will i have to do topic 2 and 3?
To Oroki :
Please Explain What Do You Mean By Topic 2 & 3
LonelyCracker said:
To Oroki :
Please Explain What Do You Mean By Topic 2 & 3
Click to expand...
Click to collapse
2. Converta stock_super.img em raw_super.img: e3. Extrato raw_super.img:
To Oroki :
Those Step You Provide Aren't Necessary Anymore
It's Patched Which Mean You Don't Have To Do Anything To It
Sorry For Late Reply
Hi everyone, this is a short guide on how to flash a GSI on the A7 Lite (without TWRP).
Its a nice little tablet for the price but it doesn't have a very powerful SOC and for me the One UI is barely usable on this device. The launcher and the whole system UI feel extremely laggy, but apps generally run fine.
I tried phhusson's custom Android 12 GSI and the device was almost resurrected. Much much less UI lag and the battery life is the same as stock ROM. The only thing i found not working is MTP but i don't need it.
Since i saw a couple users here asking about GSIs i decided to make a very simple guide.
As always do this at your own risk. You may brick your device. You will void your warranty.
Follow the guide only if you know what your are doing. Read each step carefully and avoid copy pasting stuff randomly.
I won't go deep into details as i believe you should have some basic knowledge if you decide to do this.
The procedure sould work for both T220 and T225 (i tested it on a T220).
I did this on Windows using WSL for some of the steps.
Sources
Thanks to @kkoo and @Brepro1 for the useful info
- https://forum.xda-developers.com/t/...sing-odin-without-twrp-phh-lineageos.4114435/
- https://forum.xda-developers.com/t/...r-img-and-flashing-our-modifications.4196625/
Requirements
- Unlocked bootloader
If you haven't done this already follow the steps in parts 1-2 from:
[TUTORIAL] How To Unlock & Root Tab A7 Lite T220/T225, & Install LSPosed, Magisk, Mods
While some of these instructions are copied from other sources, I combined all the different things I learned, because no one guide was sufficient, and all needed additional info, so I expanded it all to one place. Part I is partly from...
forum.xda-developers.com
- Latest official ROM
I used T220XXU1AVE1 for EUX region
Samsung Galaxy Tab A7 Lite Firmware Download SM-T220 Free Download
Samsung Galaxy Tab A7 Lite Firmware Download SM-T220 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
- Download your preferred GSI
I used AOSP 12.1 v414 with gapps from phhusson
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
- Clean vbmeta.img from Google
https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
Tools
- lz4
Releases · lz4/lz4
Extremely Fast Compression algorithm. Contribute to lz4/lz4 development by creating an account on GitHub.
github.com
- simg2img
[DEV][Tools] simg2img for Windows
Hello, although I'm working in Linux (VM too) I rewrote the SIMG2IMG so far for Windows (PE32, x86) Usage: simg2img.exe -i -o Optional: -d for debugging messages, listing all chunks of the image...
forum.xda-developers.com
- lpunpack and lpmake
[GUIDE] OTA Tools LPUnpack
Please see this URL https://android.googlesource.com/platform/build.git/+/eec4a7cba4face3370acb6293ab357879920b467 and this for more information. Hi everyone. I'm surprised I havent seen a thread about ota tools yet and lpunpack. This zip file...
forum.xda-developers.com
- tar-md5-script-tool
Use the attached tar-md5-script-tool.zip
Steps
1. Extract official ROM files (BL, AP, CP, CSC)
2. Extract AP .tar.md5
3. Decompress the extracted super.img.lz4
Code:
lz4 -d super.img.lz4 super.img
4. Convert the sparse super.img
Code:
simg2img super.img super.ext4.img
5. Unpack super.ext4.img
Code:
lpunpack super.ext4.img
I got 4 partitions in my image (should be the same for all T220/T225 ROMs):
- odm.img
- product.img
- system.img
- vendor.img
6. Replace system.img with your GSI (rename it to system.img)
7. Get the size of all partitions and the size of the original super.ext4.img (not the sparse super.img)
Code:
stat -c '%n %s' IMG_FILE.img
8. Repack super.img
Code:
lpmake --metadata-size 65536 \
--super-name super \
--metadata-slots 2 \
--device super:ORIGINAL_SUPER_IMG_SIZE \
--group main:SUM_OF_ALL_PARTITIONS_SIZES \
--partition odm:readonly:ODM_PARTITION_SIZE:main \
--image odm=./odm.img \
--partition product:readonly:PRODUCT_PARTITION_SIZE:main \
--image product=./product.img \
--partition system:readonly:SYSTEM_PARTITION_SIZE:main \
--image system=./system.img \
--partition vendor:readonly:VENDOR_PARTITION_SIZE:main \
--image vendor=./vendor.img \
--sparse \
--output ./super_new.img
Replace ORIGINAL_SUPER_IMG_SIZE, SUM_OF_ALL_PARTITIONS_SIZES, ODM_PARTITION_SIZE, PRODUCT_PARTITION_SIZE, SYSTEM_PARTITION_SIZE, VENDOR_PARTITION_SIZE with the values you obtained in step 7.
Read lpmake docs for a more detailed expalation of the args used above:
partition_tools - platform/system/extras - Git at Google
9. Compress the repacked super_new.img
Code:
lz4 -B6 --content-size super_new.img super_new.img.lz4
10. Compress the clean vmbeta.img
Code:
lz4 -B6 --content-size vbmeta.img vbmeta.img.lz4
11. Extract tar-md5-script-tool.zip
12. Put all the *.img.lz4 files extracted from AP .tar.gz in tar-md5-script-tool dir
13. Replace super.img.lz4 and vbmeta.img.lz4 in tar-md5-script-tool dir with your repacked and compressed super_new.img.lz4 (rename it to super.img.lz4) and the clean compressed vbmeta.img.lz4
14. Run batch.bat in tar-md5-script-tool dir
You will find the new AP .tar.md5 in the temp-folder subdir
15. Flash your custom AP .tar.md5 with Odin along with BL, CP, CSC from original ROM
16. Reboot into recovery and do a factory reset
17. Done
Can you share screenshot as I think treble projects are only stable on SD chipset.
Abish4i said:
Can you share screenshot as I think treble projects are only stable on SD chipset.
Click to expand...
Click to collapse
System lang is italian but should be easy to understand.
I found only a couple bugs so far in phhusson's GSI:
- in the launcher dragging apps from drawer to homescreen doesn't always work (just use another launcher)
- crashed once while searching in settings app
I use the tablet only for media consumption and some retrogaming, so there are probably other bugs i haven't noticed.
This is a generic guide, it won't include a "known issues" section since it largely depends on what GSI you choose.
I haven't tested this on the LTE version so i can't say for sure if mobile network works or not.
Unfortunately i don't have the time to make a custom ROM, test it and keep it updated here on the forum but maybe if there is enough interest someone will do it.
I hope other users will try to flash a GSI and share their experience here so we can gather some info on working/broken stuff, especially on the LTE model since i can't test that.
Hello,
I'm sorry but what am I missing here?
I'm a little fustrated cause after hours and hours of headaches I got to the second to last step which involves tar-md5-script-tool
I simply put all the .img.lz4 files from AP and replace super & vbmeta files which the ones that I converted and try to run the batch.bat as instructed.
However nothing happens and this is what the program spits out.
On the tar tool xda forum it says that it convers .img files, not .img.lz4 . Are we supposed to extract all the .img files from inside the .lz4 files?
I appreciate the guide but there are a lot of missing details I had to fill in and figure out myself, like the fact that from step 4 to step 8 you need to use WSL or a Linux distro (using simg2img for Windows messes things up so please use the one from otatools inside a linux bash)
Also for people that are not familiar with linux you need to type "./" in front of directed commands ( in this case ./simg2img ./lpunpack ./lpmake)
I'm not a developer or a programmer, maybe you wrote this guide for people more inclined to that, but for me this was pretty hard.
Noob here, but I'm running the "simg2img super.img super.ext4.img" and nothing happens for 5 min and when I'm aborting I'm getting a "Error reading sparse file header".
Any suggestions?
DanneSwe said:
Noob here, but I'm running the "simg2img super.img super.ext4.img" and nothing happens for 5 min and when I'm aborting I'm getting a "Error reading sparse file header".
Any suggestions?
Click to expand...
Click to collapse
Are you using the Windows version of simg2img? If yes, use the one from otatools inside Windows Subsystem for Linux
ReubenMCSM said:
Are you using the Windows version of simg2img? If yes, use the one from otatools inside Windows Subsystem for Linux
Click to expand...
Click to collapse
I can confirm simg2img doesn't seem to work on Windows, i used WSL.
@ReubenMCSM i will update the guide with more details in the future but i don't have much time right now.
For you specific issue, try to use the attached tar-md5-script-tool.
Great thanks!
What's the process with tar-md5-script-tool? Just moving the super.img to the folder and running the batch.bat didn't work the output file in the temp folder is 11 kb. Tried to change super.img to super.tar but no change.
Thanks for the tool, but unfortunately the output is the same, like the problem @DanneSwe has
It looks like the batch.bat script from the tar md5 tool linked in the guide is a bit different from the one i used. I will update the guide.
Try again with the version i attached in the post above.
- Extract the AP tar md5 from official rom
- Copy all .img.lz4 files in the tar-md5-script-tool folder
- Replace super.img.lz4 and vbmeta.img.lz4 (step 13)
- Launch batch.bat, output should look like this
- You will find AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5 in temp-folder
It finally worked! I redid everything and also moved my folder to drive C instead of drive D, maybe this made the difference
ReubenMCSM said:
It finally worked! I redid everything and also moved my folder to drive C instead of drive D, maybe this made the difference
Click to expand...
Click to collapse
What GSI did you pick and could you upload the files you flashed?
I got simg2img to work by using
.\simg2img -i super.img -o super.ext4.img
packed img filename: super.img
output img filename: super.ext4.img
Wrote "super.ext4.img"
The lpunpack and lpmake step isnt working for me ive been at this for days, no luck.
Can someone please help me out by uploading custom AP .tar.md5(file with GSI, the modded one) along with BL, CP, CSC from original ROM to google drive?
thanks!
ramz.pa said:
The lpunpack and lpmake step isnt working for me ive been at this for days, no luck.
Can someone please help me out by uploading custom AP .tar.md5(file with GSI, the modded one) along with BL, CP, CSC from original ROM to google drive?
thanks!
Click to expand...
Click to collapse
I had the same issue. :/
Can someone help me with the T225 LTE model by compiling the AP please? Because for some reason the tar-md5-script tool isnt working for me
Thanks.
Successfully flashed GSI with magisk on my T220 following the OP's procedure. MTP is not working as the OP said. However, I can use my flash drive so I don't really miss MTP.
I chose "system-squeak-arm64-ab-vndklite-gapps-secure.img.xz" for GSI. "Treble Info" app can tell you what image would be compatible with your device.
If you want to use a different launcher like Nova instead of the default one, change the "Smallest width" setting from 600 to 598 in Developer options to hide the annoying taskbar.
AOSP-Mods and "Project Themer - Android 12+" work fine for me.
Here is my build for my device SM-T220 (SM-T220_EUX_T220XXU1AVE1):
GSI: system-squeak-arm64-ab-vndklite-gapps-secure.img.xz
Custom AP: https://www.filehosting.org/file/details/7045394/AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5
Custom AP with Magisk patch: https://www.filehosting.org/file/details/7045714/magisk_patched-25101_cauJQ.tar
You can extract BL and Home_CSC from SM-T220_EUX_T220XXU1AVE1.
Notes: My device is actually SM-T220 XAR, but I have been updating it with SM-T220 EUX firmware versions without any issue.
Pleasance said:
Can someone help me with the T225 LTE model by compiling the AP please? Because for some reason the tar-md5-script tool isnt working for me
Thanks.
Click to expand...
Click to collapse
Here is the custom AP based on the following. Since I don't have SM-T225 device, can't verify it. However, I compiled the AP the same way I did for my SM-T220.
- SM-T225_EUX_T225XXU1AUJ1
- GSI: system-squeak-arm64-ab-vndklite-gapps-secure.img.xz
https://www.filehosting.org/file/details/7046296/AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5
xpdragon said:
Here is the custom AP based on the following. Since I don't have SM-T225 device, can't verify it. However, I compiled the AP the same way I did for my SM-T220.
- SM-T225_EUX_T225XXU1AUJ1
- GSI: system-squeak-arm64-ab-vndklite-gapps-secure.img.xz
https://www.filehosting.org/file/details/7046296/AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5
Click to expand...
Click to collapse
Thank you so much for compiling the AP for me bro but when i try to flash it with odin i get this error
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> preloader.img.lz4
<ID:0/004> FAIL!
For your information the current OS build on my tablet is INS with the baseband version of T225XXU1AVB2 and security patch of 1 Feb 2022 hope this helps you.
DanneSwe said:
What GSI did you pick and could you upload the files you flashed?
I got simg2img to work by using
.\simg2img -i super.img -o super.ext4.img
packed img filename: super.img
output img filename: super.ext4.img
Wrote "super.ext4.img"
Click to expand...
Click to collapse
GSI-12_SM-T220_EUX_T220XXU1AVE1_fac.zip
drive.google.com
Use this ONLY on SM-T220 (without SIM card) and on EUX version.
Pleasance said:
Thank you so much for compiling the AP for me bro but when i try to flash it with odin i get this error
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> preloader.img.lz4
<ID:0/004> FAIL!
For your information the current OS build on my tablet is INS with the baseband version of T225XXU1AVB2 and security patch of 1 Feb 2022 hope this helps you.
Click to expand...
Click to collapse
Here is GSI build for SM-T225_INS_T225XXU1AVB2
https://www.filehosting.org/file/details/7129248/GSI-12_SM-T225_INS_T225XXU1AVB2.zip