It seems that either Huawei have moved or removed the firmware listed at Firmware Finder, and located on dbank.
This means HiSuite Proxy won't work anymore - this is 'As Far As I Can Tell'.
As I have just discovered how to bring my P40 Pro+ back into OTA by using either Firmware Finder/HiSuite Proxy, I am particularly disappointed after all the work & also the kind help I have received that I can't complete the process and enjoy GMS + software updates.
For example, looking here, this ELS-N39-CUST 11.0.0.5(C301) firmware gives this fantastically enigmatic result: 'An error occurred.'
I am surprised the forum is not alive with discussion about this; is this the end of our ability to switch firmware or is this just a Huawei reorganisation?
I am really hoping that @IProfessor, @nomone or @realseangao (for his very useful post) are listening and can shine some light on this please.
Thank you for sharing your knowledge & hard work.
With my best regards, Kitty.
Work in progress...... 1,042 firmwares so far
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IProfessor said:
Work in progress...... 1,042 firmwares so far
View attachment 5263263
Click to expand...
Click to collapse
Thank you so very much . I await in eager anticipation, and I am relieved - it looked like 'Game Over'.
Please keep us posted .
With my best regards, Kitty.
Early version is up
Huawei Firm Finder
Quickly, easily and freely find your Huawei phone's firmware. HiSuite Proxy's official integrated firmware finder.
firmfinder.byethost5.com
any suggestion is welcomed
So many firmwares are missing, gonna add them slowly....
( The website is save-able, meaning you can save and load the "database" locally... just press CTRL + S!)
Currently targeted regions:
700 : all-cn
00 : all-cn, demo-cn
675 : hw-in
10 : hw-ru
432 : hw-eu
636 : hw-spcseas, demo-jp
185 : hw-meafnaf
781 : hw-eu
782 : hw-eu
431 : hw-eea
Discovered regions: ( would take some days / weeks to get them all in the database.... )
700 : all-cn
635 : hw-jp
786 : porsche-cn
00 : all-cn, demo-cn
675 : hw-in
10 : hw-ru
301 : channel-id
69 : telcel-mx
25 : claro-la
432 : hw-eu
636 : hw-spcseas, demo-jp
792 : hw-ca
01 : cmcc-cn
93 : channel-th
185 : hw-meafnaf
94 : hw-tr
735 : demo-cn
555 : h3g-it, h3g-gb, h3g-ie
111 : softbank-jp
130 : etcstore-th
109 : orange-all
33 : altice-all
865 : allyyqx-cn
40 : tef-normal
521 : telefonica-mx, telefonica-la
866 : alljddz-cn
819 : demo-spcseas, demo-ca, demo-meafnaf, demo-jp, demo-la
937 : allcpdz-cn
992 : rakutenmno-jp
719 : kddiuq-jp, kddi-jp
77 : hw-la
790 : demo-cmcc
16 : mtn-za
652 : demo-eu
771 : hw-la
578 : hw-ca
800 : softbankcorp-jp
02 : vodafone-es, vodafone-default
89 : demo-eea
781 : hw-eu
828 : porsche-ru
106 : ice-cr
721 : porsche-normal
782 : hw-eu
316 : vodacom-za
55 : ti-it
212 : iusacell-mx
45 : tigo-la
461 : hw-cea
346 : vha-au
605 : hw-la
431 : hw-eea
34 : optus-au
451 : telstra-au
Thanks, that was quick!
I've had a quick look (and made a small donation ) it is looking very promising, but no ELS-N39 for the UK yet.
I can see there are a lot of permutations, I am very happy to wait in the knowledge that there is a way out.
With my best regards, Kitty.
Found a strange bug that the application cannot find roms for ELS.
After a little bit more of investigation apparently, Huawei is using another method for grabbing roms for their new devices.
can you hit "Update" in HISuite then send me the
C:\Users\PCName\AppData\Local\HiSuite\log\SystemUpdate.log
file?
Also thanks for the donation really appreciated <3
I just installed HiSuite_11.0.0.510_OVE, connected my phone & ran system update; I couldn't seem to attach the log file, so here it is included:
[HiSuite_SystemUpdatelog, DIR=C:\Users\paul\AppData\Local\HiSuite\log\]
[Created Time: 2021-03-30 07:57:18:816]
[Machine: Name=KITE,Current Log Level: S3_DEFAULT_KEY]
[System Environment: OS=Windows 10 Enterprise 6.3 ; Browser=IE Version:9.11.18362.0, Default Browser:open; CPU=16 Core AMD Ryzen 7 3700X 8-Core Processor ; MEM=TotalPhys:2047MB, AvailPhys:2047MB; Disk=C:\, Free Disk:998548MB, Total Disk:1904869MB D:\, Free Disk:1165851MB, Total Disk:1907727MB E:\, Free Disk:935609MB, Total Disk:976744MB G:\, Free Disk:1888597MB, Total Disk:1907345MB; Net=Connected]
[HiSuite version: 11.0.0.510_OVE]
[2021-03-30 07:56:58:803][L2_VIM][sn=1][RESULT: TRUE][HiSuite_SystemUpdate][[[DATA1: This Phone satisfy preinstalled.[tid=26348]]]]
[2021-03-30 07:56:58:952][L2_VIM][sn=2][RESULT: TRUE][HiSuite_SystemUpdate][[[CAUSE: ?]]][[[DATA1: m_country=eu m_vendor=hw[tid=26348]]]][[[DATA2: ?]]][[[DATA3: ?]]]
[2021-03-30 07:56:59:442][L2_VIM][sn=3][RESULT: TRUE][HiSuite_SystemUpdate][[[CAUSE: ?]]][[[DATA1: hotaInfo:cVersion=C432,dVersion=D000,firmware=,imsi len=5.[tid=26348]]]][[[DATA2: ?]]][[[DATA3: ?]]]
[2021-03-30 07:57:00:768][L2_VIM][sn=4][RESULT: TRUE][HiSuite_SystemUpdate][[[CAUSE: ?]]][[[DATA1: GetSupplementPreloadBatch batch=[tid=26348]]]][[[DATA2: ?]]][[[DATA3: ?]]]
[2021-03-30 07:57:00:900][L2_VIM][sn=5][RESULT: TRUE][HiSuite_SystemUpdate][[[DATA1: GetProbufPKI key_attestantion=1560,len=1556.[tid=26348]]]]
[2021-03-30 07:57:00:900][L2_VIM][sn=6][RESULT: TRUE][HiSuite_SystemUpdate][[[DATA1: GetProbufPKI device_certificate=1648,len=1644.[tid=26348]]]]
[2021-03-30 07:57:00:900][L2_VIM][sn=7][RESULT: TRUE][HiSuite_SystemUpdate][[[DATA1: GetInfoPKI=true[tid=26348]]]]
[2021-03-30 07:57:01:022][L2_VIM][sn=8][RESULT: TRUE][HiSuite_SystemUpdate][[[DATA1: GetDisableFullbackFlag false [tid=26348]]]]
[2021-03-30 07:57:01:207][L2_VIM][sn=9][RESULT: TRUE][HiSuite_SystemUpdate][[[DATA1: IsConnectHttp.Info,s:[query.hicloud.com]p=[443][tid=26348]]]][[[DATA3: Ÿ]]]
[2021-03-30 07:57:01:254][L2_VIM][sn=10][RESULT: TRUE][HiSuite_SystemUpdate][[[CAUSE: ]]][[[DATA1:
************************* full *************************
* udid:true
* VendorCountry:hw-eu
* C_Version:C432
* D_version:D000
* DashBoard:41.003.53.00.06
* DeviceName:ELS-N39
* packageType:full
* FirmWare:
* FirmWare_Base:ELS-LGRP6-OVS 10.1.0.145
* FirmWare_Cust:ELS-N39-CUST 10.1.0.2(C432)
* FirmWare_Preload:ELS-N39-PRELOAD 10.1.0.3(C432R3)
* Language:en_US
* OS:Hisuite_11.0.0.510- Windows 10 Enterprise 6.3
* SaleInfo:|eu|hw|N|EmotionUI_10.1.0|8.6 GB||8_2.9GHz
************************************************************
[tid=26348]]]][[[DATA2: ?]]][[[DATA3: ]]]
[2021-03-30 07:57:01:254][L2_VIM][sn=11][RESULT: TRUE][HiSuite_SystemUpdate][[[CAUSE: ?]]][[[DATA1: Thread Http Request value=[tid=26348]]]][[[DATA2: https://query.hicloud.com/sp_ard_common/v2/onestopCheck.action?latest=true]]][[[DATA3: ?]]]
[2021-03-30 07:57:01:486][L2_VIM][sn=12][RESULT: TRUE][HiSuite_SystemUpdate][[[CAUSE: ]]][[[DATA1: full result body=[{"status":"1","versionPackageCheckResults":[{"status":"1","versionPackageType":2},{"status":"1","versionPackageType":3},{"status":"1","versionPackageType":4}]}][tid=26348]]]][[[DATA2: ]]]
[2021-03-30 07:58:25:881][L2_VIM][sn=13][RESULT: TRUE][HiSuite_SystemUpdate][[[CAUSE: ?]]][[[DATA1: IsConnectHttp.Info,s:[query.hicloud.com]p=[443][tid=25820]]]][[[DATA2: ?]]][[[DATA3: ?]]]
[2021-03-30 07:58:25:935][L2_VIM][sn=14][RESULT: TRUE][HiSuite_SystemUpdate][[[CAUSE: a]]][[[DATA1:
************************* full *************************
* udid:true
* VendorCountry:hw-eu
* C_Version:C432
* D_version:D000
* DashBoard:41.003.53.00.06
* DeviceName:ELS-N39
* packageType:full
* FirmWare:
* FirmWare_Base:ELS-LGRP6-OVS 10.1.0.145
* FirmWare_Cust:ELS-N39-CUST 10.1.0.2(C432)
* FirmWare_Preload:ELS-N39-PRELOAD 10.1.0.3(C432R3)
* Language:en_US
* OS:Hisuite_11.0.0.510- Windows 10 Enterprise 6.3
* SaleInfo:|eu|hw|N|EmotionUI_10.1.0|8.6 GB||8_2.9GHz
************************************************************
[tid=25820]]]][[[DATA2: C]]][[[DATA3: ]]]
[2021-03-30 07:58:25:935][L2_VIM][sn=15][RESULT: TRUE][HiSuite_SystemUpdate][[[DATA1: Http Request value=[https://query.hicloud.com/sp_ard_common/v2/onestopCheck.action?latest=true][tid=25820]]]][[[DATA2: ?]]][[[DATA3: ?]]]
[2021-03-30 07:58:26:166][L2_VIM][sn=16][RESULT: TRUE][HiSuite_SystemUpdate][[[CAUSE: ?]]][[[DATA1: SystemUpdateLogic::OnHTTPEnd body=[{"status":"1","versionPackageCheckResults":[{"status":"1","versionPackageType":2},{"status":"1","versionPackageType":3},{"status":"1","versionPackageType":4}]}][tid=26200]]]][[[DATA2: ?]]][[[DATA3: ?]]]
[2021-03-30 07:58:26:166][L2_VIM][sn=17][RESULT: TRUE][HiSuite_SystemUpdate][[[DATA1:
************************* hfull_switch *************************
* udid:true
* VendorCountry:hw-eu
* C_Version:C432
* D_version:D000
* DashBoard:41.003.53.00.06
* DeviceName:ELS-N39
* packageType:hfull_switch
* FirmWare:
* FirmWare_Base:ELS-LGRP6-OVS 10.1.0.145
* FirmWare_Cust:ELS-N39-CUST 10.1.0.2(C432)
* FirmWare_Preload:ELS-N39-PRELOAD 10.1.0.3(C432R3)
* Language:en_US
* OS:Hisuite_11.0.0.510- Windows 10 Enterprise 6.3
* SaleInfo:|eu|hw|N|EmotionUI_10.1.0|8.6 GB||8_2.9GHz
************************************************************
[tid=26200]]]]
[2021-03-30 07:58:26:383][L2_VIM][sn=18][RESULT: TRUE][HiSuite_SystemUpdate][[[CAUSE: ?]]][[[DATA1: hfull_switch result body=[{"status":"1","versionPackageCheckResults":[{"status":"1","versionPackageType":2},{"status":"1","versionPackageType":3},{"status":"1","versionPackageType":4}]}][tid=26200]]]][[[DATA3: ?]]]
[2021-03-30 07:58:26:499][L2_VIM][sn=19][RESULT: TRUE][HiSuite_SystemUpdate][[[CAUSE: ?]]][[[DATA1:
************************* full_back *************************
* udid:true
* VendorCountry:hw-eu
* C_Version:C432
* D_version:D000
* DashBoard:41.003.53.00.06
* DeviceName:ELS-N39
* packageType:full_back
* FirmWare:
* FirmWare_Base:ELS-LGRP6-OVS 10.1.0.145_EmotionUI_10.1.0
* FirmWare_Cust:ELS-N39-CUST 10.1.0.2(C432)_EmotionUI_10.1.0
* FirmWare_Preload:ELS-N39-PRELOAD 10.1.0.3(C432R3)_EmotionUI_10.1.0
* Language:en_US
* OS:Hisuite_11.0.0.510- Windows 10 Enterprise 6.3
* SaleInfo:|eu|hw|N|EmotionUI_10.1.0|8.6 GB||8_2.9GHz
************************************************************
[tid=26200]]]]
[2021-03-30 07:58:26:715][L2_VIM][sn=20][RESULT: TRUE][HiSuite_SystemUpdate][[[DATA1: full_back result body=[{"status":"1","versionPackageCheckResults":[{"status":"1","versionPackageType":2},{"status":"1","versionPackageType":3},{"status":"1","versionPackageType":4}]}][tid=26200]]]]
[2021-03-30 07:58:26:715][L2_VIM][sn=21][RESULT: TRUE][HiSuite_SystemUpdate][[[CAUSE: ]]][[[DATA1: devD[s_xxx_n],devM[ELS-N39],req[EDE9E6F437FFEC51D9CC06E01EF8BB08][tid=26200]]]][[[DATA3: ?]]]
[2021-03-30 07:58:26:931][L2_VIM][sn=22][RESULT: TRUE][HiSuite_SystemUpdate][[[CAUSE: ?]]][[[DATA1: rollback bl_result body=[{"status":"-1","errMsg":"current blVersion not found","errorCode":"100100530","blVersionCheckResults":[{"upgradePathId":0,"mccId":0,"errMsg":"current blVersion not found","errorCode":"100530","pollingPeriod":"1","blVersionInfo":{"updateAction":"rollback","laneId":581025386654073600,"laneName":"HotaLane_ELS-N39_hw_eu_C432_R3","currentBlVersionId":0,"targetBlVersionId":0,"blVersionType":1},"ruleGroupId":0,"currentVersionMatchType":0,"blVersionType":1,"status":"-1"}],"cotaInfo":{"vendorCota":"DEFAULT","country":"DEFAULT","vendorExpiredTime":"1617692306403"},"allSceneVersionQueryStatus":"0"}][tid=26200]]]][[[DATA2: A]]][[[DATA3: ?]]]
[2021-03-30 07:58:26:931][L2_VIM][sn=23][RESULT: TRUE][HiSuite_SystemUpdate][[[DATA1: reader parse format ok.[tid=26200]]]]
[2021-03-30 07:58:26:931][L2_VIM][fn=1][RESULT: FALSE][HiSuite_SystemUpdate][[[CAUSE: ERROR_CODE=-1]]][[[DATA1: invalid versionList[tid=26200]]]]
[2021-03-30 07:58:26:931][L2_VIM][fn=2][RESULT: FALSE][HiSuite_SystemUpdate][[[CAUSE: invalid.]]][[[DATA1: [tid=26200]]]]
[2021-03-30 07:58:26:931][L2_VIM][sn=24][RESULT: TRUE][HiSuite_SystemUpdate][[[CAUSE: ?]]][[[DATA1: invalid[tid=26200]]]][[[DATA2: ?]]][[[DATA3: ?]]]
[2021-03-30 07:58:26:931][L2_VIM][sn=25][RESULT: TRUE][HiSuite_SystemUpdate][[[CAUSE: ?]]][[[DATA1: Enter BL SystemFull.[tid=26200]]]][[[DATA2: ?]]][[[DATA3: ?]]]
[2021-03-30 07:58:26:931][L2_VIM][sn=26][RESULT: TRUE][HiSuite_SystemUpdate][[[CAUSE: ?]]][[[DATA1: devD[s_xxx_n],devM[ELS-N39],req[9E7D37B26803E65EA52940F14519080C][tid=26200]]]][[[DATA2: ?]]][[[DATA3: ?]]]
[2021-03-30 07:58:27:154][L2_VIM][sn=27][RESULT: TRUE][HiSuite_SystemUpdate][[[CAUSE: ]]][[[DATA1: recovery bl_result body=[{"status":"-1","errMsg":"current blVersion not found","errorCode":"100100530","blVersionCheckResults":[{"upgradePathId":0,"mccId":0,"errMsg":"current blVersion not found","errorCode":"100530","pollingPeriod":"1","blVersionInfo":{"updateAction":"recovery","laneId":581025386654073600,"laneName":"HotaLane_ELS-N39_hw_eu_C432_R3","currentBlVersionId":0,"targetBlVersionId":0,"blVersionType":1},"ruleGroupId":0,"currentVersionMatchType":0,"blVersionType":1,"status":"-1"}],"cotaInfo":{"vendorCota":"DEFAULT","country":"DEFAULT","vendorExpiredTime":"1617692306622"},"allSceneVersionQueryStatus":"0"}][tid=26200]]]][[[DATA2: ]]]
[2021-03-30 07:58:27:154][L2_VIM][sn=28][RESULT: TRUE][HiSuite_SystemUpdate][[[DATA1: reader parse format ok.[tid=26200]]]]
[2021-03-30 07:58:27:154][L2_VIM][fn=3][RESULT: FALSE][HiSuite_SystemUpdate][[[CAUSE: ERROR_CODE=-1]]][[[DATA1: invalid versionList[tid=26200]]]]
[2021-03-30 07:58:27:154][L2_VIM][fn=4][RESULT: FALSE][HiSuite_SystemUpdate][[[CAUSE: invalid.]]][[[DATA1: [tid=26200]]]]
[2021-03-30 07:58:27:154][L2_VIM][sn=29][RESULT: TRUE][HiSuite_SystemUpdate][[[CAUSE: ?]]][[[DATA1: invalid[tid=26200]]]][[[DATA2: ?]]][[[DATA3: ?]]]
The GUI response was:
I hope that helps,
Kitty.
Thank you! but deeper analytics were required, Thanks to my friend @oslo83 , figured the problem, I've ran a quick search for ELS C301 and I got the result up on the website! Check em out
Quick 18 roms for you my friend
HISuite Proxy with custom version id support
https://github.com/ProfessorJTJ/HISuite-Proxy/releases/download/2.1/HISuite.Proxy.rar
Hmmm... I think I might be being a divvy, I entered this but didn't get anything back:
Press CTRL + F5 to reload the database (it gets cached in your hardware)
Well, this is embarrassing - yes, <Ctrl-F5> refreshes (and clears out the fields) but does not return any data.
Entering data as above (Phone Model=ELS, Region (CXXX)=C301) does not return anything.
I must be doing something really stupid .
Ah. Tried it on Edge (am using Firefox) and it worked.
AndroidKittyCat said:
Well, this is embarrassing - yes, <Ctrl-F5> refreshes (and clears out the fields) but does not return any data.
Entering data as above (Phone Model=ELS, Region (CXXX)=C301) does not return anything.
I must be doing something really stupid .
Ah. Tried it on Edge (am using Firefox) and it worked.
Click to expand...
Click to collapse
Might be a bit buggy, am still trying to figure a way to refresh the database automatically when it's updated, hopefully gonna implement it as soon as today / tomorrow.
I'll also give it a go with Firefox and see what's up there, as I've been testing it with chrome only
IProfessor said:
Might be a bit buggy, am still trying to figure a way to refresh the database automatically when it's updated, hopefully gonna implement it as soon as today / tomorrow.
I'll also give it a go with Firefox and see what's up there, as I've been testing it with chrome only
Click to expand...
Click to collapse
I tried Chrome and it seemed to work really well.
My next challenge is to understand which file to upload - my phone arrived 10.1.0.176 and I simply want to update my phone to a release which will put it back in line with OTA automatic updates. I *really* don't want to go through the whole GMS palaver again if I can possibly avoid it.
I think I can phrase the above better - How can I identify firmware that will be recognised as release compatible with OTA and auto updates?
With your work, it looks like I am in serious danger of having a useful P40 Pro+. Bring it on...
Very Nice, Great Work I can you Upload 2 Firmwares for the ELS-AN10
ELS-AN10 10.1.0.150(SP1C00E150R4P1)_Firmware_general_EMUI10.1.0_05016LAG File
Meet Google Drive – One place for all your files
Google Drive is a free way to keep your files backed up and easy to reach from any phone, tablet, or computer. Start with 15GB of Google storage – free.
drive.google.com
ELS-AN10 10.1.0.155(SP1C00E155R6P1)_Firmware_EMUI10.1.0_05016LAG File
Meet Google Drive – One place for all your files
Google Drive is a free way to keep your files backed up and easy to reach from any phone, tablet, or computer. Start with 15GB of Google storage – free.
drive.google.com
Lacrimamortis said:
Very Nice, Great Work I can you Upload 2 Firmwares for the ELS-AN10
ELS-AN10 10.1.0.150(SP1C00E150R4P1)_Firmware_general_EMUI10.1.0_05016LAG File
Meet Google Drive – One place for all your files
Google Drive is a free way to keep your files backed up and easy to reach from any phone, tablet, or computer. Start with 15GB of Google storage – free.
drive.google.com
ELS-AN10 10.1.0.155(SP1C00E155R6P1)_Firmware_EMUI10.1.0_05016LAG File
Meet Google Drive – One place for all your files
Google Drive is a free way to keep your files backed up and easy to reach from any phone, tablet, or computer. Start with 15GB of Google storage – free.
drive.google.com
Click to expand...
Click to collapse
Thanks for the offer, sadly mine isn't 5G as far as I know; it's just the plain old ELS-N39 so I don't think the firmware will suit.
ELS-N39 is P40ProPlus with kirin990_5G.
Huawei is taging with N and AN its 5G models.
oslo83 said:
ELS-N39 is P40ProPlus with kirin990_5G.
Huawei is taging with N and AN its 5G models.
Click to expand...
Click to collapse
Thanks for the clarification, I found this link comparing the models and just want to install an update to the ELS-LGRP6-OVS 10.1.0.145 firmware I selected so that it will be recognised by OTA and I will be offered an automatic upgrade path.
I have managed to download some firmware from Huawei Firm Finder by using the path to the XML and replacing the XML filename with the zip filename taken from the XML file, like replacing this with this for ELS-LGRP6-OVS_11.0.0.178.
But I don't know if a) it will update or overwrite and; b) if it will be recognised and I'll be on OTA automatic updates thereafter.
Hello @IProfessor,
I found 10.1.0.176 for the eu in Huawei Firm Finder, which was the release with which my phone was pre-installed. Thanks, this is exciting!
RomID: 478415
filelist.xml
changelog_base.xml
update_full_base.zip
From changelog_base.xml, it says:
it is a security module, integrating Android security patches released in October 2020 for improved system security
the update will not erase personal data
It's around 4.5GB which looks promising.
I have no right to ask, but I'll ask anyway :
Do you know if this release will put me back on a footing where OTA will again kick in? Whilst my phone came pre-installed with 10.1.0.176, I have no idea of the original RomID
Is this a full update from a or any previous release?
I have absolutely no idea how to tell my phone to install this; I can get the zip file onto my phone but I don't know how to tell my phone to update from 10.1.0.145 with the file
Whilst the release says it will not erase personal data, I am hoping it won't touch anything else, such as my hard won (with help) GMS installation & apps I have installed.
Thank you for what you have done and your patience,
With my best regards, Kitty.
Lacrimamortis said:
Very Nice, Great Work I can you Upload 2 Firmwares for the ELS-AN10
ELS-AN10 10.1.0.150(SP1C00E150R4P1)_Firmware_general_EMUI10.1.0_05016LAG File
Meet Google Drive – One place for all your files
Google Drive is a free way to keep your files backed up and easy to reach from any phone, tablet, or computer. Start with 15GB of Google storage – free.
drive.google.com
ELS-AN10 10.1.0.155(SP1C00E155R6P1)_Firmware_EMUI10.1.0_05016LAG File
Meet Google Drive – One place for all your files
Google Drive is a free way to keep your files backed up and easy to reach from any phone, tablet, or computer. Start with 15GB of Google storage – free.
drive.google.com
Click to expand...
Click to collapse
Hello @Lacrimamortis,
Thanks for the files - much appreciated.
With my best regards, Kitty.
AndroidKittyCat said:
Hello @IProfessor,
I found 10.1.0.176 for the eu in Huawei Firm Finder, which was the release with which my phone was pre-installed. Thanks, this is exciting!
RomID: 478415
filelist.xml
changelog_base.xml
update_full_base.zip
From changelog_base.xml, it says:
it is a security module, integrating Android security patches released in October 2020 for improved system security
the update will not erase personal data
It's around 4.5GB which looks promising.
I have no right to ask, but I'll ask anyway :
Do you know if this release will put me back on a footing where OTA will again kick in? Whilst my phone came pre-installed with 10.1.0.176, I have no idea of the original RomID
Is this a full update from a or any previous release?
I have absolutely no idea how to tell my phone to install this; I can get the zip file onto my phone but I don't know how to tell my phone to update from 10.1.0.145 with the file
Whilst the release says it will not erase personal data, I am hoping it won't touch anything else, such as my hard won (with help) GMS installation & apps I have installed.
Thank you for what you have done and your patience,
With my best regards, Kitty.
Click to expand...
Click to collapse
I'd suggest you to update to a newer version rather than going back, because usually going back sometimes even bugs your phone that you need to factory reset and wipe cache for it to work.
I have put together a complete guide on how to install firmwares
Complete Guide
Modifying HiSuite and manipulating it's connection data to install Roms before they officially get released. - ProfessorJTJ/HISuite-Proxy
github.com
Related
I have problem while I am updating my GARMIN-ASUS M20's Firmware (abi).
My M20 cellphone was bought in Continental China, and I want to update to the Hongkong Chinese Firmware.
I have got the Hongkong Chinese Firmware file (.abi) and I use USBLoader in WINDOWS XP, it shows:
=====================================
#####################################################################
# USB image transfer tool for Intel PXA27X USB Development Board #
# Version: 1220'04 Author: O.C #
#####################################################################
try to open \\.\wceusbsh001
try to open \\.\wceusbsh002
try to open \\.\wceusbsh003
The file C:\M20\M20_ALL_V4.5.0.abi was opened
Image total Size 177578153 bytes
Boot record image downloading.....
File C:\M20\M20_ALL_V4.5.0.abi total 177578153 byte read
Size of ACK_PACKET = 20 address of buffer=7c92e920
=====================================
and the program just stopped here.
an hour later the program does nothing.
On my phone screen, the all status is at 0 percent.
What should I do?
ShikiSuen said:
I have problem while I am updating my GARMIN-ASUS M20's Firmware (abi).
My M20 cellphone was bought in Continental China, and I want to update to the Hongkong Chinese Firmware.
I have got the Hongkong Chinese Firmware file (.abi) and I use USBLoader in WINDOWS XP, it shows:
=====================================
#####################################################################
# USB image transfer tool for Intel PXA27X USB Development Board #
# Version: 1220'04 Author: O.C #
#####################################################################
try to open \\.\wceusbsh001
try to open \\.\wceusbsh002
try to open \\.\wceusbsh003
The file C:\M20\M20_ALL_V4.5.0.abi was opened
Image total Size 177578153 bytes
Boot record image downloading.....
File C:\M20\M20_ALL_V4.5.0.abi total 177578153 byte read
Size of ACK_PACKET = 20 address of buffer=7c92e920
=====================================
and the program just stopped here.
an hour later the program does nothing.
On my phone screen, the all status is at 0 percent.
What should I do?
Click to expand...
Click to collapse
Isn't there anyone who can help me?
ShikiSuen said:
Isn't there anyone who can help me?
Click to expand...
Click to collapse
The only thing that I can offer - read Russian forum http://asusmobile.ru/board/viewtopic.php?t=21995 using Google translate. Remember that you can see attachments in the first post with flashing instruments only if you're registered. You free to ask there in English - we will answer.
Hi guys,
today I would like to present to you a simple project that was born on this thread to accomplish a very simple task: since there are thousand of Custom ROMs around here, so much of them are LineageOS based, and because of this their forced to build every time all the ROM and post updates here. Users are also forced to check if their preferred ROM was updated or not. That's why I decided to understand how LineageOS OTA Updater System App works. Because of this I've wrote a simple REST Server API emulation that fully works with your ROM (if integrated of course). How? Continue reading down here.
How does it work?
Of course is as simple as it should be. Clone the repo (is a simple PHP website that you can host on any shared hosting*/VPS that you like) and upload it into your preferred hosting. That's it. If you point your web browser to that address the App is already working.
After, you have to upload all your build to the _builds/ folder, and you're done.
The two already working calls /api and /api/v1/build/get_delta should answer correctly the updater app to make it work (remember that visiting it as a browser is not sufficent).
How to integrate it with my ROM?
You have two options:
- Declare cm.updater.uri on your own build.prop file with the value of you own server URL where you have deployed it (This can be done also by the user with any Android App from the Market)
- Replace the string conf_update_server_url_def value inside values.xml of the OTA App source code (COMPILE TIME ONLY!)
Which builds does it support?
Anything that will be borned by the official guide on how to build your custom LineageOS ROM! So, in poor words will be: stable, rcs, nightly and snapshots (likely called EXPERIMENTAL), from CM7 to CM14.
Delta updates SHOULD work too. Just try it and tell me if they works
How can I debug it?
You can use this simple UnitTest that I've already pushed into my GitHub. Feel free to use it everytime you need. It's based upon NodeJS and Unirest.
Is it free?
"Free software is a matter of liberty, not price. To understand the concept, you should think of free as in free speech, not as in free beer."
—Richard Stallman
Click to expand...
Click to collapse
Use it as you want, do anything you want with it as it's MIT licensed.
Is it free of bugs?
That's why I'm here Only you can help me to squash all the remaining bugs!
I hope this will be useful to anyone of you, helping the ROM community providing a simple OTA updater that already works on LineageOS official ROMs.
Greets.
---
Project Home: https://github.com/julianxhokaxhiu/LineageOTA
More about the study: http://blog.julianxhokaxhiu.com/how-the-cm-ota-server-works-and-how-to-implement-and-use-ours
Changelog Build Scripts ( thanks to @Deltadroid ): https://github.com/syphyr/cm_build_scripts/blob/master/make_changelog
* On a Shared Hosting you can ONLY provide a FULL ROM download, NOT DELTAs!
---
Donators:
- @BlueFlame4 x2
Hey, I'm having trouble using your docker image behind a Nginx https reverse proxy. The server is correctly answering the requests:
Code:
{
"id":null,
"response":[
{
"incremental":"",
"api_level":"",
"url":"http:\/\/MYDOMAIN\/\/builds\/full\/lineage-17.1-20200830-UNOFFICIAL-lavender.zip",
"timestamp":1598774045,
"md5sum":"718fb89f935b979edd57b2642234d1fa",
"changes":"",
"channel":"unofficial",
"filename":"lineage-17.1-20200830-UNOFFICIAL-lavender.zip",
"romtype":"unofficial",
"datetime":1598774045,
"version":"17.1",
"id":"50533a894b2ab0d9b2711444ca4f2b530a8ff2389723ea2bd7ada6e029599e2c",
"size":914450521
}
],
"error":null
}
But the returned `url` is http-only and the updater can't download it (throws error). WhenI try to curl it without `-L` I only get `301 Moved Permanently`. Only when I append `-L` I get the correct binary response over https. I'm pretty sure this is a redirecting issue.
Here's my Nginx config:
Code:
server{
server_name MYDOMAIN;
server_tokens off;
listen 80;
listen [::]:80 ipv6only=on;
# Redirect all HTTP requests to HTTPS with a 301 Moved Permanently response.
return 301 https://$host$request_uri;
}
server {
server_name MYDOMAIN;
server_tokens off;
listen 443 ssl http2;
listen [::]:443 ssl http2 ipv6only=on;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_set_header X-NginX-Proxy true;
proxy_pass http://127.0.0.1:24087;
proxy_redirect off;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
add_header Strict-Transport-Security "max-age=15768000; includeSubdomains; preload";
add_header Referrer-Policy same-origin;
add_header X-Content-Type-Options nosniff;
add_header X-Frame-Options DENY;
add_header X-Xss-Protection "1; mode=block";
[...]
Any idea what I'm doing wrong?
Basically I want to know how to force the `url` response in the JSON to be `https` instead of `http`. (At least that's what I think is the reason for the updater not being able to download the image.)
Code:
08-30 16:00:19.407 7025 7025 D UpdaterController: Starting 50533a894b2ab0d9b2711444ca4f2b530a8ff2389723ea2bd7ada6e029599e2c
08-30 16:00:19.409 7025 7921 E HttpURLConnectionClient: Error downloading file
08-30 16:00:19.409 7025 7921 E HttpURLConnectionClient: java.io.IOException: Cleartext HTTP traffic to MYDOMAIN not permitted
08-30 16:00:19.409 7025 7921 E HttpURLConnectionClient: at com.android.okhttp.HttpHandler$CleartextURLFilter.checkURLPermitted(HttpHandler.java:124)
08-30 16:00:19.409 7025 7921 E HttpURLConnectionClient: at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:462)
08-30 16:00:19.409 7025 7921 E HttpURLConnectionClient: at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:131)
08-30 16:00:19.409 7025 7921 E HttpURLConnectionClient: at org.lineageos.updater.download.HttpURLConnectionClient$DownloadThread.run(HttpURLConnectionClient.java:250)
08-30 16:00:19.409 7025 7921 E UpdaterController: Download failed
EDIT: Solved!
Code:
location / {
proxy_pass http://127.0.0.1:24087;
proxy_http_version 1.1;
proxy_cache_bypass $http_upgrade;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
#proxy_set_header Host $host;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Port $server_port;
proxy_set_header X-NginX-Proxy true;
}
Not sure if this project is still supported, but with build.prop change, it just checks for updates forever on phone. When I try debugging with the UnitTest script, I get "Not Found The requested URL /CyanogenModOTA/api was not found on this server." (definitely server-related) I've gotten this working before on another VPS, so I'm wondering why it's not on my build server.
Are there any specific packages I need to install to get this working?
Here is my php config: http://hongbuild.ddns.net:81/test.php
klvnhng said:
Not sure if this project is still supported, but with build.prop change, it just checks for updates forever on phone. When I try debugging with the UnitTest script, I get "Not Found The requested URL /CyanogenModOTA/api was not found on this server." (definitely server-related) I've gotten this working before on another VPS, so I'm wondering why it's not on my build server.
Are there any specific packages I need to install to get this working?
Here is my php config: http://hongbuild.ddns.net:81/test.php
Click to expand...
Click to collapse
Since build.prop is in the system.new.dat file in lollipop builds, I just started copying it over from my build server and modified the Build.php file to look for the file instead of inside the zip. I just got this working on my web server. Only issue I'm having is related to change logs but I'm going to try and figure that one out later.
Here are the changes I did to get this working with CyanogenMod 12 (all changes will be assumed from the CyanogenModOTA directory):
- mkdir -p builds/buildprop <-- this is where you copy your build.prop from each build (they go in a folder with the same name as the build zip e.x. cm-12-20150103-NIGHTLY)
- mkdir -p builds/changelog <-- this will have your change logs (name them the same as the build zip except with a .txt extension)
- update setConfig( 'basePath', 'CyanogenModOTA' ) to setConfig( 'basePath', 'http://wfhome.net/CyanogenModOTA' ) in index.php (that is my server)
- change the Build constructor function to this (I updated the preg_match_all line, added the buildPropFolder variable, updated the $this->buildProp line, and changed the changeLogUrl line):
Code:
private $buildPropFolder = '';
public function __construct($fileName, $physicalPath) {
/*
$tokens Schema:
array(
1 => [CM VERSION] (ex. 10.1.x, 10.2, 11, etc.)
2 => [DATE OF BUILD] (ex. 20140130)
3 => [CHANNEL OF THE BUILD] (ex. RC, RC2, NIGHTLY, etc.)
4 => [MODEL] (ex. i9100, i9300, etc.)
)
*/
preg_match_all( '/cm-([0-9\.]+-)(\d+-)?([a-zA-Z0-9]+-)?([a-zA-Z0-9]+).zip/', $fileName, $tokens );
$tokens = $this->removeTrailingDashes( $tokens );
$this->filePath = $physicalPath . '/' . $fileName;
$this->buildPropFolder = str_replace('/full', '/buildprop', $physicalPath) . '/' . preg_replace('/\\.[^.\\s]{3,4}$/', '', $fileName);
$this->buildProp = explode( "\n", file_get_contents($this->buildPropFolder . '/build.prop') );
$this->channel = $this->_getChannel( str_replace( range( 0 , 9 ), '', $tokens[3] ) );
$this->filename = $fileName;
$this->url = $this->_getUrl( '', Flight::cfg()->get('buildsPath') );
$this->changelogUrl = str_replace('/full', '/changelog', $this->_getChangelogUrl());
$this->timestamp = filemtime( $this->filePath );
$this->incremental = $this->getBuildPropValue( 'ro.build.version.incremental' );
$this->apiLevel = $this->getBuildPropValue( 'ro.build.version.sdk' );
$this->model = $this->getBuildPropValue( 'ro.cm.device' );
}
Also he has memcached setup in there, so you might make sure you have memcache installed and set to run on startup on your server. You also need xdelta3 to create delta builds although, I don't think it is working ( I compiled the latest version of xdelta3 and it doesn't appear to do anything as there are not any files being created in the delta folder).
Hope that helps.
Thanks for the help (I'll definitely need it when I actually want to start USING the server), but it seems you've misunderstood me. Right now, I can't even get the rest server running properly-that's why I'm getting a 404 error.
Notice you get an output when you go to http://wfhome.net/CyanogenModOTA/api, I don't get anything!
klvnhng said:
Thanks for the help (I'll definitely need it when I actually want to start USING the server), but it seems you've misunderstood me. Right now, I can't even get the rest server running properly-that's why I'm getting a 404 error.
Notice you get an output when you go to http://wfhome.net/CyanogenModOTA/api, I don't get anything!
Click to expand...
Click to collapse
Ah sorry. First thing I see is that you need mod_rewrite installed in apache.
Code:
sudo a2enmod rewrite
sudo service apache2 restart
Need help with development
First I would like to thank you for using this product and playing with it (which involves patching, testing, etc.).
Since the first post I've made here in XDA the project evolved a little since I rewrote entirely the project to make it composer friendly. Rather than that, the Delta build process is actually non working (I tried to create a ZIP but I don't have enough knowledge in ROM development to tell if it's enough or not) so it's just a WIP layer that should be addressed and fixed (I've already found a Python project which does this already but I'm of the idea that this should be somehow not be a bloated software that needs to install binaries here and there to make it working).
So, actually I'm not really working in this project but It's in my TODO list, meanwhile I'll be very happy to have pull requests with useful patches to make this KK, LL and more compatible So feel free to contribute and thanks again for using it!
JulianXhokaxhiu said:
First I would like to thank you for using this product and playing with it (which involves patching, testing, etc.).
Since the first post I've made here in XDA the project evolved a little since I rewrote entirely the project to make it composer friendly. Rather than that, the Delta build process is actually non working (I tried to create a ZIP but I don't have enough knowledge in ROM development to tell if it's enough or not) so it's just a WIP layer that should be addressed and fixed (I've already found a Python project which does this already but I'm of the idea that this should be somehow not be a bloated software that needs to install binaries here and there to make it working).
So, actually I'm not really working in this project but It's in my TODO list, meanwhile I'll be very happy to have pull requests with useful patches to make this KK, LL and more compatible So feel free to contribute and thanks again for using it!
Click to expand...
Click to collapse
Thank YOU for making it! Really appreciate the time and effort you've put into this project.
rjwil1086 said:
Ah sorry. First thing I see is that you need mod_rewrite installed in apache.
Code:
sudo a2enmod rewrite
sudo service apache2 restart
Click to expand...
Click to collapse
That did it, thanks :good:
I've also implemented your changes, but when I check for updates on my phone, I still get "No new updates found". I've copied my new build over to builds/full, and the build.prop to builds/buildprop/cm*
rjwil1086 thank you very much for your help and suggestions, I made my own server http://paksman.ddns.net/cyanogenmodota, edited build.prop for cm updater to look for server url, made all the changes as you but I always get "No new updates found". Not sure if there is a problem with my server or with this project in general. Have you made any success to make this work?
I have it working. I'll upload mine to github tonight
Think I solved my own problem. My builds were all tagged as 'UNOFFICIAL'. When I changed this to 'NIGHTLY' (for the build and build.prop folder respectively ) they finally started to be recognised by cm updater app. JulianXhokaxhiu and rjwil1086, thank you so much for your effort,your work is being much appreciated.
Packsman said:
Think I solved my own problem. My builds were all tagged as 'UNOFFICIAL'. When I changed this to 'NIGHTLY' (for the build and build.prop folder respectively ) they finally started to be recognised by cm updater app. JulianXhokaxhiu and rjwil1086, thank you so much for your effort,your work is being much appreciated.
Click to expand...
Click to collapse
Yup. Sorry. I knew that but forgot to mention it. That's an issue with the CMUpdater app more than it is with the REST implementation. It doesn't look for unofficial files
Packsman said:
Think I solved my own problem. My builds were all tagged as 'UNOFFICIAL'. When I changed this to 'NIGHTLY' (for the build and build.prop folder respectively ) they finally started to be recognised by cm updater app. JulianXhokaxhiu and rjwil1086, thank you so much for your effort,your work is being much appreciated.
Click to expand...
Click to collapse
Awesome! This fixed it for me as well. Thanks to everyone for the help
[CyanogenMod][OTA][PHP] Open Source REST Server for you
Hi, I have been tested server code with a free host (000webhost) then accessed the web, I received messages:
Warning: Unexpected character in input: '\' (ASCII=92) state=1 in /home/a5885282/public_html/index.php on line 27
Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or '(' in /home/a5885282/public_html/index.php on line 27
The line 27 of index.php is "use \JX\CmOta\CmOta;". But I don't know about PHP. Please help me solve this issue.
@rjwil1086 , @klvnhng , @Packsman please help me to solve following error:
$ node index.js
<h1>500 Internal Server Error</h1><h3>Undefined offset: 0 (8)</h3><pre>#0 /var/www/CyanogenModOTA/src/Helpers/Build.php(214): flight\Engine->handleError(8, 'Undefined offse...', '/var/www/Cyanog...', 214, Array)
#1 /var/www/CyanogenModOTA/src/Helpers/Build.php(63): JX\CmOta\Helpers\Build->removeTrailingDashes(Array)
#2 /var/www/CyanogenModOTA/src/Helpers/Builds.php(115): JX\CmOta\Helpers\Build->__construct('cm-11-20140103-...', '/var/www/Cyanog...')
#3 /var/www/CyanogenModOTA/src/Helpers/Builds.php(49): JX\CmOta\Helpers\Builds->getBuilds()
#4 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Loader.php(123): JX\CmOta\Helpers\Builds->__construct()
#5 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Loader.php(80): flight\core\Loader->newInstance('\JX\CmOta\Helpe...', Array)
#6 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/Engine.php(69): flight\core\Loader->load('builds', true)
#7 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Dispatcher.php(191): flight\Engine->__call('builds', Array)
#8 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Dispatcher.php(191): flight\Engine->builds()
#9 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/Flight.php(43): flight\core\Dispatcher::invokeMethod(Array, Array)
#10 /var/www/CyanogenModOTA/src/CmOta.php(97): Flight::__callStatic('builds', Array)
#11 /var/www/CyanogenModOTA/src/CmOta.php(97): Flight::builds()
#12 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Dispatcher.php(160): JX\CmOta\{closure}()
#13 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Dispatcher.php(143): flight\core\Dispatcher::callFunction(Object(Closure), Array)
#14 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/Engine.php(310): flight\core\Dispatcher::execute(Object(Closure), Array)
#15 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Dispatcher.php(191): flight\Engine->_start()
#16 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Dispatcher.php(142): flight\core\Dispatcher::invokeMethod(Array, Array)
#17 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Dispatcher.php(48): flight\core\Dispatcher::execute(Array, Array)
#18 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/Engine.php(64): flight\core\Dispatcher->run('start', Array)
#19 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Dispatcher.php(191): flight\Engine->__call('start', Array)
#20 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Dispatcher.php(191): flight\Engine->start()
#21 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/Flight.php(43): flight\core\Dispatcher::invokeMethod(Array, Array)
#22 /var/www/CyanogenModOTA/src/CmOta.php(80): Flight::__callStatic('start', Array)
#23 /var/www/CyanogenModOTA/src/CmOta.php(80): Flight::start()
#24 /var/www/CyanogenModOTA/index.php(35): JX\CmOta\CmOta->run()
#25 {main}</pre>
Thank you so much.
Thanks all, I fixed.
[CyanogenMod][OTA][PHP] Open Source REST Server for you
I have just creat susscess a server. Thanks.
But, now I want creat a update OTA app for other AOSP ( andoird L) and using that server which I have just creat.
Can I using CMupdater for it? Can you give me some suggest?
Hi, need help to understand!
First of all, i want to say Thank You! For this great job!
I installed server, activated mod rewrite in apache2, apt-get install memcached, made chown for all files to www-data in CyanogenModOTA directory
created directories builds/buildprop, builds/changelog
created file romname.txt in changelog
copied file rom archive to build/full directory
and when i open in browser my ota site: http ota.mydomain.com i see the dir listing as described above
when i try to open url http ota.mydomain.com/api - i see the 404 error.
what exactly i have to do as the next step?
is any json file missed in web root directory (in same place as index.php) ?
and I leave index.php almost unchanged (as in the repository) - just changed string: ->setConfig( 'basePath', '/' )
Thank You once again!
vvzar said:
First of all, i want to say Thank You! For this great job!
I installed server, activated mod rewrite in apache2, apt-get install memcached, made chown for all files to www-data in CyanogenModOTA directory
created directories builds/buildprop, builds/changelog
created file romname.txt in changelog
copied file rom archive to build/full directory
and when i open in browser my ota site: http ota.mydomain.com i see the dir listing as described above
when i try to open url http ota.mydomain.com/api - i see the 404 error.
what exactly i have to do as the next step?
is any json file missed in web root directory (in same place as index.php) ?
and I leave index.php almost unchanged (as in the repository) - just changed string: ->setConfig( 'basePath', '/' )
Thank You once again!
Click to expand...
Click to collapse
Are you sure that modrewrite is working? Can you share a working URL?
lingak said:
I have just creat susscess a server. Thanks.
But, now I want creat a update OTA app for other AOSP ( andoird L) and using that server which I have just creat.
Can I using CMupdater for it? Can you give me some suggest?
Click to expand...
Click to collapse
Honestly I don't know, we have to check if OTA app is the same in Lollipop and works of course the same. If so, we're already safe and yes it can work out of the box. If not, we have to fix it. If you already have a working example, feel free to do a pull request
JulianXhokaxhiu said:
Are you sure that modrewrite is working? Can you share a working URL?
[email protected]:/home/user# a2enmod rewrite
Module rewrite already enabled
[email protected]:/home/user#
.htaccess:
[email protected]:/home/user# cat /var/www/html/CyanogenModOTA/.htaccess
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php [QSA,L]
[email protected]:/home/user#
Is any other rules i have to check?
What about statement <Directory /var/www/html/CyanogenModOTA> ?
Is enouph AllowOverride All and Allow from all ?
test url : http ota.smylink.org
Click to expand...
Click to collapse
vvzar said:
JulianXhokaxhiu said:
Are you sure that modrewrite is working? Can you share a working URL?
[email protected]:/home/user# a2enmod rewrite
Module rewrite already enabled
[email protected]:/home/user#
.htaccess:
[email protected]:/home/user# cat /var/www/html/CyanogenModOTA/.htaccess
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php [QSA,L]
[email protected]:/home/user#
Is any other rules i have to check?
What about statement <Directory /var/www/html/CyanogenModOTA> ?
Is enouph AllowOverride All and Allow from all ?
test url : http ota.smylink.org
Click to expand...
Click to collapse
Technically it should be enough but the order of where you placed it is important too.
Anyway, going to your URL is just making me think that the PHP code is running well (the redirect to builds folder is triggered by CMOTA Rest Code). You're just missing the htaccess rules.
I'm quite sure you just have to figure out your own server setup to understand if mod_rewrite is properly working (allowing htaccess files to be read and parsed).
Click to expand...
Click to collapse
[ This post a a work in progress, intended to be a tutorial but i need your help to figure out some details. ]
Hello Everyone,
This is my first post on this forum that has been oh so helpful to me these past years.
Here's the story : my rooted HUAWEI P8 Lite died, and i got myself a brand new P20 Lite that i wanted to root. Problem is HUAWEI does not provide you with the bootloader unlocking code like they did before the 12/10/2018. I mostly wanted to root the phone in order to get rid of stupid HUAWEI and Google system apps, and to be able to change the host file so that the whole world would'nt be collecting so much of my data.
But I was f*cked, it's impossible to get your hands on a bootloader unlocking code unless you pay for it.
/// THE DEVICE ///
Huawei P20 LITE (ANE-LX1)
Firmware version 8.0.0.149(C109)
Not rooted (it's the point of this thread)
/// HOW TO GET RID OF SYSTEM APPS ///
I met a guy that told me that system apps could be removed using ADB, he pointed out this method that was very useful to me and i'm here to share it with you guys.
This is where he saw the trick : https://forum.xda-developers.com/android/general/uninstall-apps-via-adb-t3738105
So basically all you need to know is the name of the app package you are trying to remove, very luckily, there's an app that does just that, it's called "apps_Packages Info" and you can get it on F Droid. https://f-droid.org/packages/com.oF2pks.applicationsinfo/
Using these two things, i was able to remove some nasty stuff. The list of what i already removed is available here : https://github.com/Zblay/Cleaning_HUAWEI_P20/blob/master/ADB_Commands.txt
I would like to finish this list, so it could be re-used by anybody wanting to clean his HUAWEI the same way i did.
But there are some package from Huawei i don't know whether or not i can remove without damaging the system, if you know these packages can be removed safely or replaced by an open-source alternative, please tell me
- HUAWEI
Capture d'écran défilant : com.huawei.HwMultiscreenShot
Capture d'écran vidéo : com.huawei.screenrecorder
com.huawei.hiviewtunnel
com.huawei.iaware
déverrouillage intelligent : com.huawei.trustagent
Diagnostic Intelligent : com.huawei.hwdetectrepair
Dock de navigation : com.huawei.android.FloatTasks
FIDO UAF ASM : com.huawei.hwasm
FIDO UAF Client : com.huawei.fido.uafclient
Fonction Push : com.huawei.android.pushagent
Gestionnaire de téléphone : com.huawei.systemmanager
Huawei déverrouillage Magazine : com.android.keyguard
Huawei share : com.huawei.android.internal.app
huawei.android.widget
HwAps : com.huawei.android.hwaps
HwChrService : com.huawei.android.chr
HwImsService : com.huawei.ims
HwIndexSearchObserverService : com.huawei.indexsearch.observer
HwIndexSearchService : com.huawei.indexsearch
HwInstantOnline : com.huawei.android.instantonline
HwIntelligentRecSystem : com.huawei.recsys
HwLBSService : com.huawei.lbs
HwNearby : com.huawei.nearby
HwStartupGuide : com.huawei.hwstartupguide
HwSynergy : com.huawei.synergy
HwUE : com.huawei.bd
HwWifiproBqeService : com.huawei.wifiprobqeservice
Importer via bluetooth : com.huawei.bluetooth
Message de dimensionnement : com.huawei.omacp
MMITest : com.huawei.mmitest
Partage Wi-Fi Direct : com.huawei.android.wfdft
Power Genius : com.huawei.powergenie
ProjectMenu : com.huawei.android.projectmenu
Service d'autenthification : com.huawei.trustcircle
Services du système huawei : com.huawei.systemserver
TIPS : com.huawei.tips
TME : : com.huawei.tmecustomize
-GOOGLE
Carrier Services : com.google.android.ims
Service Google Play : com.google.android.gms
Service de tranfert : com.google.android.backuptransport
Programme d'installation : com.google.android.packageinstaller
Print Service Recommandation : com.google.android.printservice.recommendation
Market FeedBack Agent : com.google.android.feedback
-OTHER
Android Easter Egg : com.android.egg
Maybe there is a place on the internet where i could learn more about all of these packages ? do you know such a place ?
/// HOW TO PREVENT TRACKERS FROM SPYING ON YOU ///
Exodus Privacy app helped me get a decent diagnosis of what nasty trackers were in my apps ( yes i would like to use non-open-source apps, because some are useful ) https://exodus-privacy.eu.org/en/
I'm currently hesitating between DNS66 app and Blockada app, what do you guys think ?
Thanks a lot for helping me out. :good:
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.
PHP:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
FEATURES
. The first, the one and the only custom vendor for dynamic partition in the world : I challenge you all to show me who did it before !
. If you find any custom rom with similar work since the first release of this one : it is just a copied and a stolen work [fake Google roms +++] !!!
. Compatible with all regions / basebands / firmwares / device variants
. Works with All AOSP/CAF based ROMs [10] & [11], Experimental, Official & Unofficial [TESTED]
. May works on fake Google roms but i don't take any responsibility
. Mount RO/RW available with no bootloop after reboot ! [Magisk/SU required]
. SafetyNet passed
. Full test passed : audio, ril, wifi, bt, fm radio, camera, sensors, fp scanner, nfc, ...
. All known hardware issues on custom roms are fixed : camera, wifi, bt, hdr playback, chrome ... and overheating !
. Custom Kernel with stock zImage [untouched +++]
IMPORTANT !
. NO firmware change is needed from the user side, so don't repeat this question many times ... just read up again !
. Formatting /data is required when you flash this vendor the first time +++
. Never go back to the previous versions due to the possible build.fingerprint change [Old releases are automatically removed] +++
. Dirty Update : always delete with file/root explorer or in TWRP this folder :
/data/property and reboot
You must delete these files & folders in /product partition from your custom rom
[File/Root explorer needed] :
/product/vendor_overlay/29/etc/audio
/product/vendor_overlay/29/etc/audio_policy_configuration.xml
/product/vendor_overlay/29/etc/audio_policy_engine_configuration.xml
/product/vendor_overlay/29/lib/soundfx
/product/vendor_overlay/29/lib64/soundfx
&
/product/vendor_overlay/29/etc/wifi
/product/vendor_overlay/29/overlay
& finally
/product/vendor_overlay/29/etc/qdcm_calib_data_nt36672c_huaxing_fhd_video_mode_dsi_panel.xml
/product/vendor_overlay/29/etc/qdcm_calib_data_nt36672c_tianma_fhd_video_mode_dsi_panel.xml
Already included in this vendor ... and since i'm the original author !
[ OPTIONAL ]
If you have the madness and the paranoia with security like Google, you can still relock /vendor again to the stock RO state ... But you will not be able to mount /vendor RW again even with root until you reflash the provided vendor.zip again !
How to [terminal or adb shell] :
su
tune2fs -O verity /dev/block/dm-1
*******
!!!
MIUI Users : sorry for you, but this is for custom ROMS " ONLY "
TROLLS & NOOBS, stay away ... Please !
!!!
Prerequisite:
POCO X3 NFC = surya
POCO X3 [no NFC] = karna
No matter where you live : india, china, russia, europe, usa or africa ... !
Kernel Source [Prebuilt] : Here
Created : 2021-02-27
Latest Update : 2021-03-21
DOWNLOAD
RESERVED for "Changelog"
Update : [2021-03-21] Highly Recommended !
- overlay folder [/vendor] : secure & total remove ... R.I.P forever !
You can now remove it from here too ... with no issue :
/product/vendor_overlay/29/overlay
[As always : no /data formatting is required if done in the previous builds !]
Update : [2021-03-20]
fix compatibility with all custom roms [10] & [11] +++ :
- build : preserve AVB structure [R/W still available in root mode]
- tune2fs : restore some stock feature flags [dir_index, huge_file, extra_isize]
- fstab [kernel & vendor] : small update
- vendor selinux : property_contexts fix
- build.prop : clean-up
Update : [2021-03-18]
clean-up & rework from scratch :
. all audio config [over 20 files +++]
. all media_codecs config
. new mixer_paths
[=> Exclusive]
- true resampling fix : r.i.p audio crackling and all audio issues in UX, Dialer, emulators ... etc [forever]
- improve audio & camera recording
- audio/video playback [Speaker, Headphones & BT] : Hi-Fi quality, loud & noiseless
[but first, you must delete these files with your File/Root Explorer:
/product/vendor_overlay/29/etc/audio
/product/vendor_overlay/29/etc/audio_policy_configuration.xml
/product/vendor_overlay/29/etc/audio_policy_engine_configuration.xml
/product/vendor_overlay/29/lib/soundfx
/product/vendor_overlay/29/lib64/soundfx]
Update : [2021-03-12]
- move to global 12.0.8.0 as firmware base [boot & vendor]
- ramdisk :
. disable mi_thermald and re-enable again thermal-engine
[on all custom roms : mi_thermald breaks the proximity sensor & suspend service in deepsleep => avoid hand wave gesture & AOD to work properly !]
. clean up & update
- vendor_selinux : add more camera permissions in property_contexts
- media_codecs : remove unused .xml
- ueventd.rc : rework from scratch
Update : [2021-03-07]
- ramdisk :
. update cpuset & schedtune settings
. improve memory multitasking
. make that "damn" fingerprint truly responsive
. enable UFS powersaving
. some clean-up & disable MIUI audio service
- media_profiles :
. rework from scratch
. add slow motion profile support : up to 1080p/120 fps & 720p/960 fps
. front video camera : add 4K support
- build.prop :
=> update parameters for : camera, ril, performance, playback ... and more
Update : [2021-03-05]
- rework from scratch : init.qcom.sh & init.qcom.post_boot.sh
- ramdisk : clean-up and add init.qcom.power.rc
. fix CPU instability : set 300 mHz as CPU minimum frequency for all cores / update schedutil governor parameters
. cpu_boost : improve touch responsiveness
. add built-in display power saving [for both huaxing & tianma panels]
- vendor permissions : rebuild from scratch / fix wronlgy settled paths (by Xiaomi) in some qti.xml
- camera : rework from scratch ISO/lowlight config
- remove dummy hbtp folder ... since there is no binary to load or device specific config
- targetconfig : update CoreCtlCpu to [0,6]
- build.prop : clean up and move NFC parameters to build_surya.prop
- [Bonus] : Wi-Fi signal improved (x2) !!!
. 2.4 Ghz : 144 => 300
. 5 GHz : 433 => 866
[but first, you must delete this folder, with your File/Root Explorer :
/product/vendor_overlay/29/etc/wifi ]
Update : [2021-03-01]
- update msm_irqbalance.conf
- update audio_effects.conf & remove audio_effects.xml
- universal vbmeta & vbmeta_system added
Update : [2021-02-27]
- initial release
- rework all build.prop (vendor & odm) from scratch
- debloated from unused MIUI folders, files & configs
- Kernel :
. enforcing selinux by default
. workqueue enabled in cmdline => better dynamic refresh rate handling by the CPU & stellar deep-sleep
. fstab reworked from scratch
the image you made is for enable rw or not?
my phone is poco x3 nfc surya
janhammer504 said:
To make things clear :
POCO X3 NFC = surya
POCO X3 (no NFC) = karna
No matter where you live (india, china, russia, europe, usa or africa) ... Choose the right vendor.img for your device !
[Both images were tested by me]
Click to expand...
Click to collapse
please share the surya image
aallii2 said:
please share the surya image
Click to expand...
Click to collapse
check the DOWNLOAD link up !
janhammer504 said:
check the DOWNLOAD link up !
Click to expand...
Click to collapse
tnx bro i'm downloading n i'll test
its not working after restart didnt boot n just go to recovry
aallii2 said:
its not working after restart didnt boot n just go to recovry
Click to expand...
Click to collapse
Wich firmware version you had just before flashing ???
The vendor provided must match the firmware version that you have !!!
janhammer504 said:
PREREQUISITE
- adb enabled (developer options)
- root (Magisk/SU)
- adb for Windows (Minimal ADB and Fastboot, provided)
- USB cable always connected
LIVE Flashing :
adb shell
su
dd if=/sdcard/vendor.img of=/dev/block/dm-1
View attachment 5232189
Reboot your phone right away ... then use your File/Root Explorer to test the mount RO/RW option and reboot again to check that there is no bootloop !
(Optional)
If you have the madness and the paranoia with security like Google, you can still re-enable AVB/Verity again ... But you will not be able to mount /vendor RW again even with root until you reflash the provided vendor.img again !
tune2fs -O verity /dev/block/dm-1
Check the full tutorial here to build your own custom vendor ... if you want !
DOWNLOAD
Click to expand...
Click to collapse
... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)...
... Thank you very much for your hard work...
just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...
jeryll said:
... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)...
... Thank you very much for your hard work...
just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...
Click to expand...
Click to collapse
i use adb shell because terminal is too small for me, and for making tutorial.
the benefit ??? well there are a bunch of fixes to do in /vendor... check here for example
(the images i provided are clean with no modification, so i let developers or users doing their own modifications)
janhammer504 said:
Wich firmware version you had just before flashing ???
The vendor provided must match the firmware version that you have !!!
Click to expand...
Click to collapse
india 12.0.9
magisk 21.4
jeryll said:
... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)...
... Thank you very much for your hard work...
just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...
Click to expand...
Click to collapse
hey bro how you flashed in orangefox?
i tried but this happened:
sh: adb: command not found
aallii2 said:
hey bro how you flashed in orangefox?
i tried but this happened:
sh: adb: command not found
Click to expand...
Click to collapse
in recovery adb not needed, just use
dd if=/sdcard/vendor.img of=/dev/block/dm-1
now i cant install any rom :
updater process ended with error 7
pls help
aallii2 said:
now i cant install any rom :
updater process ended with error 7
pls help
Click to expand...
Click to collapse
O.M.G
it looks like you never used terminal
this is not a flashable file, it's a command line.
open terminal in your recovery to do that.
or use adb shell
janhammer504 said:
O.M.G
it looks like you never used terminal
this is not a flashable file, it's a command line.
open terminal in your recovery to do that.
or use adb shell
Click to expand...
Click to collapse
jeryll said:
in recovery adb not needed, just use
dd if=/sdcard/vendor.img of=/dev/block/dm-1
Click to expand...
Click to collapse
Now this came:
write error: Operation not permitted
jeryll said:
in recovery adb not needed, just use
dd if=/sdcard/vendor.img of=/dev/block/dm-1
Click to expand...
Click to collapse
Now this came:
write error: Operation not permitted
Use Minimal ADB and Fastboot.zip, it's the simplest and the fastest way.
Unzip and click on Minimal ADB and Fastboot.exe
type :
adb shell
su
It works like terminal in Windows. You can't go wrong !
Follow the instructions (1 post) !
aallii2 said:
india 12.0.9
magisk 21.4
Click to expand...
Click to collapse
wtf man, you should pick vendor.img from karna folder not surya !
janhammer504 said:
Use Minimal ADB and Fastboot.zip, it's the simplest and the fastest way.
Unzip and click on Minimal ADB and Fastboot.exe
type :
adb shell
su
It works like terminal in Windows. You can't go wrong !
Follow the instructions (1 post) !
Click to expand...
Click to collapse
i installed 12.0.7.0 global with magisk 22.0 then flashed vendor.img v12.0.7.0 but when restarted it stucked n i pressed power .phone boot but root explorer can't mount rw n just added shell in magisk