Related
I think this is a known issue...is there a fix ?
my MLA-L03 is ugraded to Nougat /Emui 5...
Version MLA-L03C654B300 custc654d001
On Aida64 it says...
api level 24...
CodeName REL...
TAGS,Release keys...
(if you need more info's,just ask)
is there a way to make the theme manager work again ?
or i will have to wait for this version to be updated by huawei/android...
could someone share the theme manager APK (if its doable of course)
phone is running perfectly,for now,ive installed ADWLauncher for a bit of theme
but now that ive played a bit with nougat/emui5,if i had the choice,i would'nt do the upgrade to nougat/emui5...i prefer the way that emui4.1 was presented for the look n feel
thanks in advance for helping me fix this theme manager problem
I have tried to install the theme manager from here https://forum.xda-developers.com/p9/themes/apps-huawei-stock-updated-apps-android-t3412464
and, when clicking Install,it ends with...
APK not installed ,looks like a corrupted file
try http://update.hicloud.com:8180/TDS/...ers_ca/update_data_full_MLA-L03_rogers_ca.zip
dont know if that is right data zip but should be!
i think u need next to the upgrade also data zip file
that is exactly what i already have but thanks anyway
After update my theme manager is not working as well. Though i haven't seen it working on EMUI 4. Now it is just blank. I think there should be some theme from internet like recomended or others. I have downloaded a theme from internet and put it i HWthemes folder and it showed in manager but applying it changed nothing.
Welcome to the club...
I think that it may have something to do with update process, now i'm stuck on NRD90M test-keys build number which i think is incorrect.
I'm about to update again manually later this day.
Me and my wife have the same phone...she received the official ota and she does have the same thing as i do...with release keys written...and theme managets is working on her phone... Both our phones are identical now but...my theme manager is not working
I fixed it.
Ive downloaded update.zip and update_data_full_CAN-L11_hw_eu.zip from this website stechguide. com (look for CAN-L11C432B340 update and followed the instructions do flash it. After that the themes are working, i also have some more Hi...apps, it fixed the build numer and i have Update in menu.
I dont think it will wor for me...im on mla-l03c654b334...
virusdunil said:
I dont think it will wor for me...im on mla-l03c654b334...
Click to expand...
Click to collapse
I installed the hw package for my MLA-L03 C654B334 after installing the full rom from FF and I still don't have themes or the update app. Actually nothing really changed but the proper build number. Think I may try a stock recovery factory reset and dalvic/cache wipe and start with a clean slate instead of the dirty flash i did to get here through the various FF releases.
I think we cant rollback to MM due to file system changes ... ( i think)
virusdunil said:
I think we cant rollback to MM due to file system changes ... ( i think)
Click to expand...
Click to collapse
No not yet. Unless you can find someone with MM version for our variant that can make twrp backups, then we can use those to roll back but I can't find any for the MLA-L0X anywhere.
Also can run Lineage OS13 if coming from MM as an option to Emui 4. But not if already on Nougat.
WHY is it so long to find a fix for that theme manager problem ?
Why dont we have support from Huawei about that?
Why is HUAWEI not responding to our emails...?
Is someone here trying to find a fix ?
is someone at HUAWEI trying to find a fix ?
So many questions.............................................................................................. but no answers...........................
Maybe that is an interesting fact...
ive tried to install official emui5.0 apk from different sources...
install directly via phone failed as corrupted files...
install via Hisuite,it says wrong signature,installation aborted.
ive found honor9 nougat/emui5 camera apk so tried the same thing...
both methods ended as failed so...
is it really an apk signature problem for our theme manager ???
a corrupted firmware
or a fault in firmware via FF ???
Try this one - it comes from my Nova CAN-L01 updated to EMUI 5
Hi...and thanks...ive dloaded it and install,like all the others ive tried failed saying file may be corrupted
Its always the same thing
Strange. Maybe the problem is that it's system app and it needs some additional libraries or it need to be installed in system/app folder. In that case you'll need root. Are you on official update or you just flashed an update from firmware finder?
Firmware finder
Well than maybe it was some release not in final stage. I just recieved offocial update and theme manager is working fine.
https://www.google.com/amp/s/forum....ed/unofficial-systemless-xposed-t3388268/amp/
The thing is.... I went to the app to get the program and Magisk wouldn't install the program on it's end. Took a shot and installed the apk (SDK 25), then installed the 88.1 version shown in the picture (now 88.2) rebooted and waited to "upgrade" itself.... But here it is plain as day. I'm not saying you may get it running on yours but it worked for me. Happy testing y'all,
SykkNyzz
And apparently Gravity Box for Nougat just came out 2 days ago at the time of this post.
Just ticked to center the time. Perfecto.
Reboot and such work as well
Nav Bar as well (note swapped buttons and added menu)
Even the Expanded Desktop works.
I can't get any modules to install in magisk on this phone. Tried systemless Xposed and nothing. How did you install it?
That looks like system install. Systemless usually says it like in this screenshot.
Did you install magisk with the zip in recovery, or modified boot.img? Systemless Xposed would be nice, hoping to get working on mine.
madbat99 said:
I can't get any modules to install in magisk on this phone. Tried systemless Xposed and nothing. How did you install it?
That looks like system install. Systemless usually says it like in this screenshot.
Did you install magisk with the zip in recovery, or modified boot.img? Systemless Xposed would be nice, hoping to get working on mine.
Click to expand...
Click to collapse
I couldn't use the Magisk even to this moment. I just used the apk listed above and did it that way
SykkNyzz said:
I couldn't use the Magisk even to this moment. I just used the apk listed above and did it that way
Click to expand...
Click to collapse
OK. I got system install working on mine too. Yours looks like system install too, not systemless. The xposed app downloads normal system install. You should change the name of the thread since it's not actually systemless. Just to avoid confusion.
madbat99 said:
OK. I got system install working on mine too. Yours looks like system install too, not systemless. The xposed app downloads normal system install. You should change the name of the thread since it's not actually systemless. Just to avoid confusion.
Click to expand...
Click to collapse
Well, the app itself from the website is stated as such. As where I can see where you are coming from. Thank you for the heads up.
SykkNyzz said:
Well, the app itself from the website is stated as such. As where I can see where you are coming from. Thank you for the heads up.
Click to expand...
Click to collapse
I can't get any magisk modules to work either, I was genuinely hoping you had it here. I've noticed you're pretty active in the forums for this phone.
Glad you showed xposed working, it helped me decide to try it.
Okay so everything was working fine up until yesterday. Then i uninstalled a theme and applied it again with a different accent color, and it didnt apply. I tried it with other themes and overlays and they werent compiling either. I tried uninstalling all overlays and now i cant get any themes to work. It says compiled without any errors when i build it but after i reboot my device theres nothing there, the theme hasnt applied at all. Anybody know what happened??
If your running a custom rom than it is probably sue to the system partition being full and therefore Substratum cant work.
Sarim26 said:
Okay so everything was working fine up until yesterday. Then i uninstalled a theme and applied it again with a different accent color, and it didnt apply. I tried it with other themes and overlays and they werent compiling either. I tried uninstalling all overlays and now i cant get any themes to work. It says compiled without any errors when i build it but after i reboot my device theres nothing there, the theme hasnt applied at all. Anybody know what happened??
Click to expand...
Click to collapse
Archangel said:
If your running a custom rom than it is probably sue to the system partition being full and therefore Substratum cant work.
Click to expand...
Click to collapse
Im on stock android 9.0
Well then thats def weird my themes run perfect so far. Are you making sure that you go back into Substratum manager and enabling all overlays that you previously built after rebooting?
\
Sarim26 said:
Im on stock android 9.0
Click to expand...
Click to collapse
Archangel said:
Well then thats def weird my themes run perfect so far. Are you making sure that you go back into Substratum manager and enabling all overlays that you previously built after rebooting?
Sarim26 said:
Im on stock android 9.0
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Thats the problem, after i reboot nothing shows up in the manager, they never compiled even though it says compiled without any errors before the reboot
Hi there,
I'm facing the same issue at the moment... @op did you find the culprit?
Cheers...
Same here. Anytime got any ideas? Magisk installed, root granted, stock 9.0. Themes compiled and visible in Substratum. I install overlays, see nothing in Manager tab (which is normal), get no errors, reboot, and still nothing in Manager tab.
First update since installing Lineageos on Lenovo P2.
The navigation bar along the bottom disappeared. Couldn't be swiped up - had been fixed previously.
Then found other things as well. Fingerprint sensor not working. Pixel launcher failing. Had been using Nova launcher and foolishly removed it thinking I'd reinstall to see if it restored the nav bar. But now stuck with a failing launcher and can't start anything - including Play to reinstall Nova. Just says 'Pixel Launcher keeps stopping, App info, Close App.' Cleared cache from App info as that was all I could do but no difference.
I haven't read it anywhere but are updates cumulative? Ie, can I skip one if I miss it and get all updates rolled up into the next one. I hope so because that's what I did. Jumped from something like 9th August to 30th.
Any ideas?
Current update always include codes from previous builds so you can skip nightlies in between. There are few solutions for your problem. I'm telling you two:
1. Install a third party launcher apk through system settings
2. Reboot into TWRP, wipe system only and install latest update package with nano gApps and it should work.
alirazaagha said:
Current update always include codes from previous builds so you can skip nightlies in between. There are few solutions for your problem. I'm telling you two:
1. Install a third party launcher apk through system settings
2. Reboot into TWRP, wipe system only and install latest update package with nano gApps and it should work.
Click to expand...
Click to collapse
Thanks so much for your help. In fact, while trying your first suggestion I somehow got into Google Play through APK install settings from where I was able to reinstall Nova Launcher. So now I have a partly useable phone again but still with the problems that followed the update in my OP (navigation bar gone, fingerprint sensor stopped working plus the failing launcher - those are just the things I found without looking).
It's disappointing that the update failed though, not least as staying updated was a major reason for moving to Lineage. Any ideas why this might be?
Maybe I should try the second suggestion and reinstall the update by sideloading as described here. So do I use the same file that I use to install LineageOS in the first place from here https://download.lineageos.org/kuntao? It's not stated in the document. And will this wipe the phone clean again?
Finally would I have to re-sideload a GApps package at the same time and should it be Nano GApps as suggested? Originally I installed Open GApps as suggested in the upgrade instructions.
bind00 said:
Thanks so much for your help. In fact, while trying your first suggestion I somehow got into Google Play through APK install settings from where I was able to reinstall Nova Launcher. So now I have a partly useable phone again but still with the problems that followed the update in my OP (navigation bar gone, fingerprint sensor stopped working plus the failing launcher - those are just the things I found without looking).
It's disappointing that the update failed though, not least as staying updated was a major reason for moving to Lineage. Any ideas why this might be?
Maybe I should try the second suggestion and reinstall the update by sideloading as described here. So do I use the same file that I use to install LineageOS in the first place from here https://download.lineageos.org/kuntao? It's not stated in the document. And will this wipe the phone clean again?
Finally would I have to re-sideload a GApps package at the same time and should it be Nano GApps as suggested? Originally I installed Open GApps as suggested in the upgrade instructions.
Click to expand...
Click to collapse
The Pixel launcher in Android 10 force closes if it is not chosen as "Recents provider". Therefore, navigation bar also stops working. Hence, we need Quickswitch app to choose Pixel or any other launcher such as Lawnchair for giving them the mentioned right and that works without any hiccups.
You should install the latest update after wiping system only. You don't need to wipe everything, just wipe system partition.
Nano GApps are taken from Open Gapps website. I've suggested nano GApps because it doesnt include Pixel Launcher hence, stock ROM launcher will flawlessly work. However, if you want to use Pixel Launcher then install Magisk from recovery and Quickswitch module within Magisk. Then open Quickswitch app from launcher and click Pixel Launcher. Quickswitch app will process for a few moments and will restart your phone. Now, choose Pixel launcher as default from settings if it is not used as default and Done.
alirazaagha said:
The Pixel launcher in Android 10 force closes if it is not chosen as "Recents provider". Therefore, navigation bar also stops working. Hence, we need Quickswitch app to choose Pixel or any other launcher such as Lawnchair for giving them the mentioned right and that works without any hiccups.
You should install the latest update after wiping system only. You don't need to wipe everything, just wipe system partition.
Nano GApps are taken from Open Gapps website. I've suggested nano GApps because it doesnt include Pixel Launcher hence, stock ROM launcher will flawlessly work. However, if you want to use Pixel Launcher then install Magisk from recovery and Quickswitch module within Magisk. Then open Quickswitch app from launcher and click Pixel Launcher. Quickswitch app will process for a few moments and will restart your phone. Now, choose Pixel launcher as default from settings if it is not used as default and Done.
Click to expand...
Click to collapse
Many thanks again for your detailed help. Much appreciated.
Went for standard Open GApps just because that's what I had before and had hoped to get it all back as it was. (I've no particular preference for Pixel only that was all that was available to me after updating through updater. ) I've got the update loaded now, sideloaded with adb and TWRP. Unfortunately I seem to have accidentally factory reset from TWRP (thought I was just swiping to unlock and only noticed too late. Doh.)
TBH, this has been a whole lot of hassle for an update. After hours to get this far now have to set phone up from scratch yet again. And crucially, I still don't know why updater failed. Going to be very nervous about running update in future and staying updated was the main point of moving to Lineage in the first place.
But thanks for help again.
bind00 said:
Many thanks again for your detailed help. Much appreciated.
Went for standard Open GApps just because that's what I had before and had hoped to get it all back as it was. (I've no particular preference for Pixel only that was all that was available to me after updating through updater. ) I've got the update loaded now, sideloaded with adb and TWRP. Unfortunately I seem to have accidentally factory reset from TWRP (thought I was just swiping to unlock and only noticed too late. Doh.)
TBH, this has been a whole lot of hassle for an update. After hours to get this far now have to set phone up from scratch yet again. And crucially, I still don't know why updater failed. Going to be very nervous about running update in future and staying updated was the main point of moving to Lineage in the first place.
But thanks for help again.
Click to expand...
Click to collapse
No problem bro. Next time, when you update, follow these things:
1. Keep ROM, Magisk and GApps in a single folder.
2. When updating ROM, just install the ROM and restart.
alirazaagha said:
No problem bro. Next time, when you update, follow these things:
1. Keep ROM, Magisk and GApps in a single folder.
2. When updating ROM, just install the ROM and restart.
Click to expand...
Click to collapse
Thanks again. That's good information. So you recommend not using the Updater but adb sideloading instead?
OK, and I just read this at stackexchange "You normally don't need to re-flash GApps as most GApps installers will install an addon.d script which restores GApps automatically after flashing a new ROM that supports addon.d (LineageOS does so)." So if GApps is in the same folder it finds it automatically I guess.
I'd better clue myself up on Magisk now and a decent backup system.
cheers
bind00 said:
Thanks again. That's good information. So you recommend not using the Updater but adb sideloading instead?
OK, and I just read this at stackexchange "You normally don't need to re-flash GApps as most GApps installers will install an addon.d script which restores GApps automatically after flashing a new ROM that supports addon.d (LineageOS does so)." So if GApps is in the same folder it finds it automatically I guess.
I'd better clue myself up on Magisk now and a decent backup system.
cheers
Click to expand...
Click to collapse
Built in update works as required but if it messes with system partition then you better download update and install it through recovery.
GApps can be restored after update but the point is that you don't need it. System update only replaces the older system files with new ones without touching gApps files. Whereas, Magisk is automatically installed after update if it's in the same folder.
Hello,
I have a brand new device which has not officially been released yet. Therefore, there is no stock firmware image available or recovery image. Just wanted to get that out of the way. I could not remove a lot of the manufacturers bloatware because i could not root or port TWRP without a stock image or recovery image.
I stumbled onto Project Treble. I flashed phh treble and it worked. Well, I managed to get everything to work with some workarounds. The only thing I am having trouble with is when I install phh with gapps. After booting I get the "Your device is not Google certified" message repeatedly spammed.
The only workaround I have been able to get to work for the uncertified device message is to remove phh superuser. I have tried using the Google device registration page. It does not work for my device. I want to keep root so I can pull the recovery image and port TWRP for this device. Are there any other fixes that will work? In order to pick up in some of my games I think I need Google Play?
Thanks,
Rocky
What Gapps? you can try bitgapps, opengapps, etc...
If google play is impossible, you can download .apk android apps (Android PacKage, APK) from www.uptodown.com, www.apkmirror.com and www.apkpure.com, unless it is google play exclusive(probably payment content?)
LR7875 said:
What Gapps? you can try bitgapps, opengapps, etc...
If google play is impossible, you can download .apk android apps (Android PacKage, APK) from www.uptodown.com, www.apkmirror.com and www.apkpure.com, unless it is google play exclusive(probably payment content?)
Click to expand...
Click to collapse
Thanks for your reply. Yes, I need to recover paid content. There are games and programs that I have spent a decent amount on that I would like to have access too. I wish there was a phh gsi image with magisk root instead of phh root. From what I read you can disable it with Magisk.
I do not know a whole lot about root. I wonder if now that I am using phh gsi if it would be possible to install Magisk now? I could not install it before because the device does not have a system image available yet since it has not officially been released. Like I said I do not know much about root, could I just download a vanilla phh gsi image and patch that with magisk?
bigroc2223 said:
Thanks for your reply. Yes, I need to recover paid content. There are games and programs that I have spent a decent amount on that I would like to have access too. I wish there was a phh gsi image with magisk root instead of phh root. From what I read you can disable it with Magisk.
I do not know a whole lot about root. I wonder if now that I am using phh gsi if it would be possible to install Magisk now? I could not install it before because the device does not have a system image available yet since it has not officially been released. Like I said I do not know much about root, could I just download a vanilla phh gsi image and patch that with magisk?
Click to expand...
Click to collapse
No no no, you need to patch boot.img for magisk, not system. Go to www.apkmirror.com (app repository), search and download 'magisk ' app(that is magisk manager), click and install the downloaded .apk file, allow install from browser, and after installing use the app to patch the boot.img(search Google), and flash patched boot.
I thought I bricked the phone but was able to recover. I am getting an error that I cannot seam to resolve. The phone screen will go black. It goes to a crash dump screen that says the fallowing.
Qualcomm Crash Dump Mode
modem subsystem failure reason
trm_rf_alloc.cpp:459:allocation
not found for RF Tech:2 Band:126
sub_capability 0.
After this happens and I reboot the device I have a hard time getting mobile data to work. It is definitely an error pertaining to the signal radio. I have no clue how to fix it. With this happening the device is pretty much unusable.
bigroc2223 said:
I thought I bricked the phone but was able to recover. I am getting an error that I cannot seam to resolve. The phone screen will go black. It goes to a crash dump screen that says the fallowing.
Qualcomm Crash Dump Mode
modem subsystem failure reason
trm_rf_alloc.cpp:459:allocation
not found for RF Tech:2 Band:126
sub_capability 0.
After this happens and I reboot the device I have a hard time getting mobile data to work. It is definitely an error pertaining to the signal radio. I have no clue how to fix it. With this happening the device is pretty much unusable.
Click to expand...
Click to collapse
I am sorry to hear that.It is pretty much beyond what I can solve so I will try find similar threads.