Database Develop

HTC One - Couldn't Install on USB Storage or SD Card

Hi there!
I received my HTC One two days ago and I am unable to install any PAID apps on the phone. I am able to install free apps without an issue though.
I have searched all over the internet and found two possible solutions, which don't work. These solutions were:
Unmount the SD card. Install app, remount the SD card. This won't work as the HTC One does not have an SD card
In the secure/asec folder, find and delete "smdl2tmp1.asec". Although I found the folder, it was empty and therefore I was unable to delete the file.
I have also completely wiped my phone twice already. I checked the Kernel and Firmware version and it's all up to date. Below are screenshots of the device info.
{
"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"
}
Finally, I also realized, only after I paid for the device, it's a Dev device. I don't know if this makes any difference though.
The bootloader is unlocked and the device has been rooted. I have full access over the file system.

Make a nandroid and flash another rom to see if that fixes it.

You're using an old custom ROM! Flash any new ROM of your choice from the dev section and it should fix the problem. The issue is within the kernel.
StephanBotha said:
Hi there!
I received my HTC One two days ago and I am unable to install any PAID apps on the phone. I am able to install free apps without an issue though.
I have searched all over the internet and found two possible solutions, which don't work. These solutions were:
Unmount the SD card. Install app, remount the SD card. This won't work as the HTC One does not have an SD card
In the secure/asec folder, find and delete "smdl2tmp1.asec". Although I found the folder, it was empty and therefore I was unable to delete the file.
I have also completely wiped my phone twice already. I checked the Kernel and Firmware version and it's all up to date. Below are screenshots of the device info.
Finally, I also realized, only after I paid for the device, it's a Dev device. I don't know if this makes any difference though.
The bootloader is unlocked and the device has been rooted. I have full access over the file system.
Click to expand...
Click to collapse

Hi,
I'm having a similar problem to the OP. I have a GPE HTC One which is rooted and S-Off. I just updated the software from 4.4 to 4.4.2, at which point the inability to update or install paid apps appeared. As in the original post, I can't find the smdl2tmp1.asec. In fact, my entire mnt/secure folder is empty, as is mnt/asec. I also don't have a .android_secure folder, as has been mentioned in other posts. If I restore to a previous backup running 4.4, everything works fine. The issue is only with installs or updates from the Play Store, because I am able to install the apps from my Titanium backups just fine, but when I do, I get the same error message when I try to update them.
Thanks

roman1984 said:
Hi,
I'm having a similar problem to the OP. I have a GPE HTC One which is rooted and S-Off. I just updated the software from 4.4 to 4.4.2, at which point the inability to update or install paid apps appeared. As in the original post, I can't find the smdl2tmp1.asec. In fact, my entire mnt/secure folder is empty, as is mnt/asec. I also don't have a .android_secure folder, as has been mentioned in other posts. If I restore to a previous backup running 4.4, everything works fine. The issue is only with installs or updates from the Play Store, because I am able to install the apps from my Titanium backups just fine, but when I do, I get the same error message when I try to update them.
Thanks
Click to expand...
Click to collapse
Hi,
I have this exact same issue. Nothing in secure folder etc. From 4.4 to 4.4.2 via OTA.

roman1984 said:
Hi,
I'm having a similar problem to the OP. I have a GPE HTC One which is rooted and S-Off. I just updated the software from 4.4 to 4.4.2, at which point the inability to update or install paid apps appeared. As in the original post, I can't find the smdl2tmp1.asec. In fact, my entire mnt/secure folder is empty, as is mnt/asec. I also don't have a .android_secure folder, as has been mentioned in other posts. If I restore to a previous backup running 4.4, everything works fine. The issue is only with installs or updates from the Play Store, because I am able to install the apps from my Titanium backups just fine, but when I do, I get the same error message when I try to update them.
Thanks
Click to expand...
Click to collapse
The only fix for this is to install Android Revolution ROM. At least, that's the only way I could fix mine :crying:

You should always use stock recovery for OTA updates. This problem is probably due to applying the OTA with a custom recovery.

BenPope said:
You should always use stock recovery for OTA updates. This problem is probably due to applying the OTA with a custom recovery.
Click to expand...
Click to collapse
That's unfortunate, since I like twrp. To reinstall stock recovery, do I just flash the image like I did with twrp?

Yes. You can put TWRP back on after the OTA is on.

BenPope said:
Yes. You can put TWRP back on after the OTA is on.
Click to expand...
Click to collapse
Thanks, that did the trick. Going back and forth between recoveries like that is a little annoying, but fortunately it's relatively quick, so it's not horrible.

roman1984 said:
Thanks, that did the trick. Going back and forth between recoveries like that is a little annoying, but fortunately it's relatively quick, so it's not horrible.
Click to expand...
Click to collapse
Did you have to go back to TWRP and reinstall the GPe ROM? Or did you just have to flash TWRP and it started working again?

DyingBlade said:
Did you have to go back to TWRP and reinstall the GPe ROM? Or did you just have to flash TWRP and it started working again?
Click to expand...
Click to collapse
Once I was able to update using the stock recovery, all I had to do was flash TWRP and everything worked fine (no need to reinstall the GPE ROM since that was already running).

[4.4.4][XT1039][OFFICIAL][TWRP/CWM] Stock Moto G 4G 21.1.46.en.EU

Stock with unlocked bootloader warning removed
Motorola 4G 4.4.4 Kitkat for EUROPE/AUSTRALIA aka XT1039
This is for unlocked bootloader only
Update brings:​
Android 4.4.4 Kitkat
SD Card Fixes
Instructions:
FLASH CWM
WIPE DATA/FACTORY RESET
FLASH ROM
FLASH Super SU (if you want to root)
WIPE DALVIK.
ENJOY!
Only tested with CWM
Dowload:​
Mega
Google Drive
If you want another filehost just ask and if the zip does not work tell me we will look into it :highfive:​

OMG!!!
About root procedure... Did anyone know about it?

Flash this Super SU
Ps: Is my update working ?

I didn't try it yet. I prefer TWRP, so I was going to test if it's working with it. But I just got the XT1039 last week, so I set it up to my liking, then I unlocked bootloader to root it, so second setup, and then I messed up deleting some files (don't really know what happened), so I had to set it up for the 3rd time just yesterday. I'm not in the mood of wiping it again just yet!
But i will
EDIT: Just installed it, with TWRP and wiping only cache. Works like a charm!

I did the update with the file above without any wipe (except cache)
Envoyé de mon XT1039 en utilisant Tapatalk

It works perfectly, thank you!
I was having some trouble updating to 4.4.4 using OTA as I changed a lot in the stock rom. After spending hours reverting changes, I still couldn't get it to work (without flashing stock and starting all over again, which I didn't want to do really).
Was thinking of starting all over again, flashing stock image, OTA to 4.4.4 and changing everything after that, when I came across your thread.
You saved me from spending hours having to start from scratch! Top job!
I only flashed your file from my OTG drive in TWRP , over my heavily changed system, and it works like a dream.
See this screenshot I took right after flashing and reboot:
{
"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"
}
So, yes man, you did it! Thanks again! [emoji106]
Verstuurd vanaf mijn XT1039 met Tapatalk

Nice work Darius.
Also had probs with 4.4.4 OTA due to custom recovery/rooting.
This was easiest way to 4.4.4 happiness....

I want to try this one, but I want to know how can I verify that bootloader is locked or not, and how can I unlock it.
Any threat talking about this?
PD: Could be unlocked from adb typing "fastboot oem unlock"?

Will this work for the XT1039 from Great Britain? Build numbers are the same but instead of EU there is a GB. I bought mine from Amazon and it is the unlocked version.

Awesome!
Hi,
Just installed on my 4.4.3, wiping only the cache partition as you said. As far as I can see everythying works perfectly.
Thank you man !

guijarrelson said:
I want to try this one, but I want to know how can I verify that bootloader is locked or not, and how can I unlock it.
Any threat talking about this?
PD: Could be unlocked from adb typing "fastboot oem unlock"?
Click to expand...
Click to collapse
The bootloader is proprietary so you need to ask Motorola for an unlock code. "Fastboot oem unlock" won't work. There are a lot of threads about this in Q&A and General.

I just finished updating my GB version to this EU version and it worked great! No issues to report. Installed CWM recovery, then EU 4.4.4., wiped cache then installed superuser. Fantastic work with no lost data. My 32GB sdcard works too!!!! AMAZING

I tried using a Sandisk 32 Gb sd card (bought in 2011, and still working perfectly in my old HTC Desire) that didn't work in this phone before the update, but it still doesn't. Have seen other reports about the same issue, so I guess not every sd card problem is solved with the 4.4.4 update.
The card mounts normally, I can see the files on it in any explorer, but it's not possible to read from or write onto the card.
Phone can't format the card, and a check with a Windows pc doesn't show anything wrong with the card.
Strange huh? Any ideas?

I've flashed this and all is working but I can not enable ART can someone else let me know if they can or can't please?

mhisani said:
I've flashed this and all is working but I can not enable ART can someone else let me know if they can or can't please?
Click to expand...
Click to collapse
Do you have xposed framework installed? Art doesnt work with it so...
Second, do you have enough internal memory free?

jkoetsier said:
Do you have xposed framework installed? Art doesnt work with it so...
Second, do you have enough internal memory free?
Click to expand...
Click to collapse
I factory reset the device and still I could not. I flashed the rom via recovery and that seemed to solve it.. perhaps xposed changed something that was not cleared on wipining

mhisani said:
I factory reset the device and still I could not. I flashed the rom via recovery and that seemed to solve it.. perhaps xposed changed something that was not cleared on wipining
Click to expand...
Click to collapse
Factory Reset does not touch your system partition. Only wipes your data.
Xposed would have modified your system partition to prevent ART. Flashing a new rom would restore your system partition to how it was.
Next time, either disable xposed before uninstalling. Or if that doesn't work, either fastboot flash the system.img chunks found in the stock firmware OR flash the same firmware in a custom recovery (if zip available). This will refresh your system partition and restore any changes without affecting your data.

Edit: ignore

Wait so will this work on the XT1045?

I have flashed this ROM and my SD card (Sandisk 16 GB) is still not recognized by the phone. Any advices ?

Official Rom update - P7-L10V100R001C00B133SP01

{
"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"
}
We were offered an update in Czech Republic B133 .
She was offered only to users who have the B121 , the higher the update, update not comming .
So I made a downgrade from B126 to B121 and then the B133 via OTA .
I Uploaded my downloaded update.zip , but I do not know how you could install it .
I'm sure someone here will tell .
Here we therefore give the B133 update.zip , original downloaded via OTA , but discussed this how to install it. :good:
1. Improved stability roaming
2. Czech user manual
3. Improved system stability
4. Mode Smart -Cover
5. Sound Enhancement
6. corrects an error for the following applications: WhatsApp and Wechat (delayed release) , Camera , Office, Music
Dovnload update.zip B133 here:
http://ulozto.cz/xHESUQkU/update-zip#download
If someone comes to how to install this update.zip , I love and pass it on.

jkmaxfli said:
We were offered an update in Czech Republic B133 .
She was offered only to users who have the B121 , the higher the update, update not comming .
So I made a downgrade from B126 to B121 and then the B133 via OTA .
I Uploaded my downloaded update.zip , but I do not know how you could install it .
I'm sure someone here will tell .
Here we therefore give the B133 update.zip , original downloaded via OTA , but discussed this how to install it. :good:
1. Improved stability roaming
2. Czech user manual
3. Improved system stability
4. Mode Smart -Cover
5. Sound Enhancement
6. corrects an error for the following applications: WhatsApp and Wechat (delayed release) , Camera , Office, Music
Dovnload update.zip B133 here:
http://ulozto.cz/xHESUQkU/update-zip#download
If someone comes to how to install this update.zip , I love and pass it on.
Click to expand...
Click to collapse
You should create a folder with 'dload' name in SD card root and copy the 'update.zip' into the folder. Then open the System Update app and choose Local update.
The software finds the zip and starts the update process. Done.

I've tried but i get fail, and it doesn't update. My region is Spain, and the current versión is B126
Enviado desde mi HUAWEI P7-L10

It seems that the update will only work on the B121
Some screens:

I did a downgrade to 121, try to search an udpate via ota, but the only one that appears was b126, so i used the dload metod, coping the file in, and chossing local update. Everything seems to be working fine for me at the moment.
If you want to install you need to have 121 version.

mud_f1 said:
I did a downgrade to 121, try to search an udpate via ota, but the only one that appears was b126, so i used the dload metod, coping the file in, and chossing local update. Everything seems to be working fine for me at the moment.
If you want to install you need to have 121 version.
Click to expand...
Click to collapse
OTA only update if you on b121 with czech sim card

what a bout network ver & also what a bout sms problems is it solved ?

Just updated my phone into B133... Observing..........

I get a fail too with update.zip in root, with update.zip in dload, with update.zip renamed to update.app in dload and with just the unpacked update.app in the dload.
All fail.
I am on B126 though...I love it so much I don't have the heart to download to B121 for a firmware I don't know anything about!
So I'll wait for you all to test it!
Sent from my HUAWEI P6-U06 using XDA Premium HD app

I am under B127SP02. Will try to upgrade and let u know.
The only problem is that I see five files named update.zip; which is the one to download ?

kolembo said:
I get a fail too with update.zip in root, with update.zip in dload, with update.zip renamed to update.app in dload and with just the unpacked update.app in the dload.
All fail.
I am on B126 though...I love it so much I don't have the heart to download to B121 for a firmware I don't know anything about!
So I'll wait for you all to test it!
Sent from my HUAWEI P6-U06 using XDA Premium HD app
Click to expand...
Click to collapse
I also tried B126 to update into B133. But it wont work. All you have to do is to downgrade your firmware into B121. Anyway, you don't need to backup your data. Just downgrade it normally into B121. After downgrading into B121, proceed upgrading into B133.

majcomtech said:
I also tried B126 to update into B133. But it wont work. All you have to do is to downgrade your firmware into B121. Anyway, you don't need to backup your data. Just downgrade it normally into B121. After downgrading into B121, proceed upgrading into B133.
Click to expand...
Click to collapse
can you give me working link to download B121

haninatoon said:
can you give me working link to download B121
Click to expand...
Click to collapse
http://4pda.ru/pages/go/?u=http://android-host.de/HUAWEI/P7/B121SP01/B121SP01.zip
Sent from my HUAWEI P7-L10 using Tapatalk

haninatoon said:
can you give me working link to download B121
Click to expand...
Click to collapse
B121: http://www.huaweidevices.de/ascend-p7?show=downloads
This steps might help you.
5.1 Normal downgrade
Step 1. A MICRO SD card of 4GB or more should be available. The MICRO SD card made by Sandisk, Kingstone, or Kingmax is recommended.
Step 2. Format the MICRO SD card (This operation is optional).
Step 3. Copy the entire dload folder (B121) (dload, with UPDATE.APP in it) to the root directory of the MICRO SD card.
Step 4. Insert the MICRO SD card into the handset and power on. After entering the home screen, run Settings->Updates->System updates->Local update->Confirm->Upgrade to start the downgrade.
After downgrading:
1. Download B133 firmware.
2. Delete UPDATE.APP from the dload folder from your SD card.
3. Copy and paste update.zip in dload folder from your sd card.
The proceed with normal upgrade.
Step 1. Run Settings->Updates->System updates->Local update->Confirm->Upgrade to start the upgrade.

I am still on B121. I didn't update to B126 either because there is no notification came up on my phone. Is there anything good in these updates?

rifad20 said:
I am still on B121. I didn't update to B126 either because there is no notification came up on my phone. Is there anything good in these updates?
Click to expand...
Click to collapse
1. Improved stability roaming
2. Czech user manual
3. Improved system stability
4. Mode Smart -Cover
5. Sound Enhancement
6. corrects an error for the following applications: WhatsApp and Wechat (delayed release) , Camera , Office, Music
Sent from my HUAWEI P7-L10 using Tapatalk

b133 firmware update
Dear All!
I have just joined to this community. It looks very good and informative.
I've just updated my P7 to firmware B133. What I'm missing from my phone is the startup manager. I hoped if I do this update this feature will appear in my options. But it did not. Could someone please tell me which update contains the Startup manager?
I have another question. If I download a firmware update from a german webpage (for me it seems firmware updates only available to download from webpages from germany) will it contain other languages (i.e. hungarian)?
Thank in advance!
Peter from Hungary
(sorry for my bad english)

Available as OTA in Croatia also. I'm on B121, downloading now.

Does anyone noticed battery drains faster?
Enviado desde mi HUAWEI P7-L10

hmedved said:
Available as OTA in Croatia also. I'm on B121, downloading now.
Click to expand...
Click to collapse
Malaysia here also received OTA of B133,
current also @ B121,updated now....55%....
---------- Post added at 02:42 PM ---------- Previous post was at 02:40 PM ----------
mud_f1 said:
Does anyone noticed battery drains faster?
Enviado desde mi HUAWEI P7-L10
Click to expand...
Click to collapse
Normally it need few cycle of charging to stable down after updating new firmware,keep observe....

[GUIDE] Unbrick Huawei P8 Lite 2017 PRA-LX1 No Brand

Hi folks
When I get back the device from Huawei services, I receive a boot.img without encryption that let me able to backup and restore the firmware hundred times without errors .
In this tutorial I'll show you how to do that without need to bring the phone to Huawei services to reset the software, starting from now can be done as well.
Requirements:
Unlocked bootloader, you know how to do that.
My own TWRP, that authorized Huawei store told should use my own TWRP to restore the phone, so get it from here by downloading the latest version.
Stock firmware, click here to download it, it's for single sim only.
Stock IMGS that needed for decrypt and to re-enable the encryption once firmware has been done with restoration, click here to download them.
7 zip to unpack the tar.gz.
Code:
[CENTER][COLOR="Red"][SIZE="4"][FONT="Comic Sans MS"]Please read the steps carefully because I'm not going to repeat them for each user, thanks[/FONT][/SIZE][/COLOR][/CENTER]
Reset Steps:
Download the C432B161.
Unpack the .tar.gz archive with 7 zip.
{
"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"
}
Rename from C432B161 to TWRP.
Copy to the Internal Storage.
Reboot to TWRP Recovery by the following command.
in the IMGS archive you will find a bootimage called boot.img, rename it to boot.emmc.win and copy to TWRP->BACKUPS->57UDU17709001769->2017-10-18--12-03-00_NRD90M_test-keys -> replace it and then follow the video
Go to the TWRP.
Wipe everything except the external_sd (the path where you copy the backup)
Tab on Restore.
Choose the copied backup make sure to rename from C432B161 to TWRP to match.
Select all partitions.
Swipe the screen and wait until finish.
Reboot to bootloader once done.
In the IMGS.tar.gz there is a file caller boot.img flash via fastboot as boot and will get booted like charm
Warning:
You are not allowed to copy or steal the files of my guide without ask my permissions.
Because I take almost week to upload the firmware after many times of failing upload.
Mention this guide for who looking helps to restore this device.
If I saw any piece of my contents in other threads, I'll report as abuse and ask a moderator to close his thread because I already saw someone rename my recovery and put it inside his thread without asking permission. that's all.
This guide could be helpful for who want to debrand his device, so we need tester.
to enable dual sim: you must flash an oeminfo partition from dual sim firmware.
Happy restoring.

Can I change from dualsim to monosim with this guide?

Wire1122 said:
Can I change from dualsim to monosim with this guide?
Click to expand...
Click to collapse
to be honest, I can't confirm since is the full backup from my single device.
in case dual sim still appear even after restore, you have to flash the single sim oeminfo partition.

when I must flash oeminfo?

Wire1122 said:
when I must flash oeminfo?
Click to expand...
Click to collapse
post firmware restoring

Wire1122 said:
when I must flash oeminfo?
Click to expand...
Click to collapse
not works to me. Pralx1c432b182 such before restoring

Wire112233 said:
not works to me. Pralx1c432b182 such before restoring
Click to expand...
Click to collapse
whats not work restoring firmware or converting from dual to single?

haky 86 said:
whats not work restoring firmware or converting from dual to single?
Click to expand...
Click to collapse
converting from dual to single. But after restoring the fw remains b182, not 161

Wire112233 said:
converting from dual to single. But after restoring the fw remains b182, not 161
Click to expand...
Click to collapse
yup because some partitions is upgraded to b182 (dual sim), same thing happen to me b181 (single sim). for converting to single sim, I'll upload the oeminfo partition soon.
Note: this operation might will lock bootloader/frp automatically, so I recommend to check them via fastboot mod.

When oeminfo?
Sent from my HUAWEI PRA-LX1 using XDA Labs

Looks like the images gone bad, and now point:
Wipe the following partitions like in the screenshot.
Click to expand...
Click to collapse
can be quite challenging
Wiped cache/data/system and restored everything that I was allowed to from your backup.
Meanwhile I changed name of directory: TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\9DC7N17A17006059\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu.
(Hope that didn't change anything?)
Then I completed your "Reset Steps" tutorial, reboot and [...]
that hilarious green screen is still in place of previous Huawei:
After initial configuration my first impression was that I downloaded wrong backup, cause it looks more like the Elite ROM V6 (5 icons at bottom-screen menu, google searchbar, additional options (4 rows instead of 2) in upper-scroll menu and the pinkish-purple wallpaper) even the blinking NFC problem I had with that ROM is present there, but yet it's not that one. All informations in settings>about phone are from your backup, I even checked if the Android Studio will find my phone - and it did! That was unavaible in HassanMirza01's ROM.
So there's my question - does it suppose to look that way? Or I just messed something really hard and the visual theme files from previous OS's stayed somehow on my phone?
Don't take me wrong - after this tutorial I ended up with fully functional, nice looking (as soon as I change the pinkish wallpaper...) smartphone, so I'm really happy thanks to you!
Anyway I found it also interesting how the GreenScreen could ended up in such a place, so I'll try to figure that out.

Sixter said:
Looks like the images gone bad, and now point:
can be quite challenging
Wiped cache/data/system and restored everything that I was allowed to from your backup.
Meanwhile I changed name of directory: TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\9DC7N17A17006059\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu.
(Hope that didn't change anything?)
Then I completed your "Reset Steps" tutorial, reboot and [...]
that hilarious green screen is still in place of previous Huawei:
After initial configuration my first impression was that I downloaded wrong backup, cause it looks more like the Elite ROM V6 (5 icons at bottom-screen menu, google searchbar, additional options (4 rows instead of 2) in upper-scroll menu and the pinkish-purple wallpaper) even the blinking NFC problem I had with that ROM is present there, but yet it's not that one. All informations in settings>about phone are from your backup, I even checked if the Android Studio will find my phone - and it did! That was unavaible in HassanMirza01's ROM.
So there's my question - does it suppose to look that way? Or I just messed something really hard and the visual theme files from previous OS's stayed somehow on my phone?
Don't take me wrong - after this tutorial I ended up with fully functional, nice looking (as soon as I change the pinkish wallpaper...) smartphone, so I'm really happy thanks to you!
Anyway I found it also interesting how the GreenScreen could ended up in such a place, so I'll try to figure that out.
Click to expand...
Click to collapse
might the elite rom v6 cause that issue, try to restore it again perhaps it will gone..I didn't get that green and red screen

Hey, any have oeminfo for single sim fw? its impossible to find

http://www.mediafire.com/file/0tnrmliuudsz9qo/OemInfo_EU_SS.zip
https://mega.nz/#F!0xcUWCBZ!FAXGLF3WC_uFsc5r--BqEQ

Wire1122 said:
http://www.mediafire.com/file/0tnrmliuudsz9qo/OemInfo_EU_SS.zip
https://mega.nz/#F!0xcUWCBZ!FAXGLF3WC_uFsc5r--BqEQ
Click to expand...
Click to collapse
Thanks for the help! For what version is this oem? (b161?)

dannyzamora said:
Thanks for the help! For what version is this oem? (b161?)
Click to expand...
Click to collapse
I don't know Sorry It is monosim c432

Wire1122 said:
I don't know Sorry It is monosim c432
Click to expand...
Click to collapse
Thx! One question... I have now installed b182, can i "downgrade" installing the b161 twrp backup with the tutorial and later install this oem?
Enviado desde mi PRA-LX1 mediante Tapatalk

dannyzamora said:
Thx! One question... I have now installed b182, can i "downgrade" installing the b161 twrp backup with the tutorial and later install this oem?
Enviado desde mi PRA-LX1 mediante Tapatalk
Click to expand...
Click to collapse
even if downgraded will keep on b182 because some partitions will not downgraded since my twrp is designed to backup/restore only necessary partitions for fully worked firmware.

I also had to rename TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\<my device ID visible in adb devices>\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu, thanks @Sixter. Please update the first page accordingly.
But even doing so, when coming to Huawei eRecovery I'm still stuck with "Getting package info failed" issue, I cannot get back EMUI yet. Any hint?

bagage said:
I also had to rename TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\<my device ID visible in adb devices>\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu, thanks @Sixter. Please update the first page accordingly.
But even doing so, when coming to Huawei eRecovery I'm still stuck with "Getting package info failed" issue, I cannot get back EMUI yet. Any hint?
Click to expand...
Click to collapse
You might want to try the Recovery MITM approach but its a tad more complicated. https://forum.xda-developers.com/p8lite/p8-lite-2017-discussion/guide-local-recovery-server-t3714900

EMUI 9 root updates

I just looked up a few threads about rooting EMUI 9.
The one and only who kinda managed to do it is the developer of Magisk John Wu.
If you wanna stay updated about rooting EMUI 9 on Huawei P20pro, you should follow this guy:
EMUI9 root
still NO EMUI 9 kernel sources released

Rooting / Magisk is one thing. I think in addition to that we also need a working twrp or some recovery for Emui 9 to be able to flash stuff with relative ease. On top of that the OEM unlock option is greyed out which is problematical itself. So, this is all gonna be a bit complicated.

Well, there is a modded versions of TWRP Mate Rs Porsche with working decryption and for most people including me, oem-unlock is not greyed out when you have unlocked frp and unlocked bootloader.
I'm on the final of EMUI 9. So the last important thing would be a rooted EMUI 9 to get some important things working.
mrabcx said:
Rooting / Magisk is one thing. I think in addition to that we also need a working twrp or some recovery for Emui 9 to be able to flash stuff with relative ease. On top of that the OEM unlock option is greyed out which is problematical itself. So, this is all gonna be a bit complicated.
Click to expand...
Click to collapse

ArtaxXP said:
and for most people including me, oem-unlock is not greyed out when you have unlocked frp and unlocked bootloader.
Click to expand...
Click to collapse
Unlocked frp = oem unlock enabled in dev options
Unlock bootloader and frp itself doesn't cause "enable oem unlock" being greyed out. It's not getting greyed out just by upgrading to pie either. Upgrade to pie and factory reset does!
Good to know about twrp working on p20 pro

Hello, i changed my system font by using huawei themes.
Now it's not possible anymore, to edit photos and use different fonts for editing.
Does anybody have an idea, what i can do?i want to keep the new system font.
I hope to get a usefull help, i really would be grateful.
Sorry for this comment, i doesn't belong at this page

there is already something new on this topic?

not much but some
Heinzx3 said:
there is already something new on this topic?
Click to expand...
Click to collapse

some good news
good news

Rooted on 9.0
{
"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"
}
Sent from my CLT-L04 using Tapatalk

Dene_Bluesman said:
Rooted on 9.0 View attachment 4673784
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Yeah awesome! Well done!
John Wu just released some info in a post: EMUI9 root

Dene_Bluesman said:
Rooted on 9.0 View attachment 4673784
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Link pls

mr.mgmg said:
Link pls
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sent from my CLT-L04 using Tapatalk

Dene_Bluesman said:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
There are alot files
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Any file i must download and flash

mr.mgmg said:
There are alot files
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Any file i must download and flash
Click to expand...
Click to collapse
Would like someone to drop round and flash it for you too? Do some reading, or don't flash.

purple patch said:
Would like someone to drop round and flash it for you too? Do some reading, or don't flash.
Click to expand...
Click to collapse
I think the Q not for you, just keep silent

mr.mgmg said:
I think the Q not for you, just keep silent
Click to expand...
Click to collapse
his point is, even you got the question wrong,
no files from that list will root your emui 9 simply by flashing any of it,
you gonna need a copy of RECOVERY_RAMDIS.img pulled from update.app of latest emui 9.0 firmware,
copy it to device with latest canary magisk & magisk manager installed,
patching the .img using that canary manager, and you will get patched_boot.img stored in download folder in that device,
copy it to your pc and flash it to recovery_ramdisk partition using fastboot,
or if you really are that lazy, simply download the prepatched one here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
and flash it from fastboot to your recovery_ramdisk partition
boot by holding vol up button

otonieru said:
his point is, even you got the question wrong,
no files from that list will root your emui 9 simply by flashing any of it,
you gonna need a copy of RECOVERY_RAMDIS.img pulled from update.app of latest emui 9.0 firmware,
copy it to device with latest canary magisk & magisk manager installed,
patching the .img using that canary manager, and you will get patched_boot.img stored in download folder in that device,
copy it to your pc and flash it to recovery_ramdisk partition using fastboot,
or if you really are that lazy, simply download the prepatched one here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
and flash it from fastboot to your recovery_ramdisk partition
boot by holding vol up button
Click to expand...
Click to collapse
Thanks for help

It will seem dumb for some of you but important to me and others (i Hope there are some lol)..... so just to be clear :
1- do we have to follow these steps AFTER installing emui 9 ? coming from emui 8.1 161 with evira kernel and using mods i wanna start 100% fresh because first time i installed emui 9 163 i came back a week later because of battery consuption that was way worse and real bad SOT so it's major to me to proceed the best way - i have to go first to twrp and wipe all, data+system+caches before flashing emui 9 ?
2- any reason not to use the easiest way ? why to prefer the complicated one : pulling the file from update.app and copy and etc....?
3- magisk modules will be usable ?
Thanks to those of you who will bring light or give me confident in re-installing pie.
And of course merry Christmas everyone

deltaman83 said:
It will seem dumb for some of you but important to me and others (i Hope there are some lol)..... so just to be clear :
1- do we have to follow these steps AFTER installing emui 9 ? coming from emui 8.1 161 with evira kernel and using mods i wanna start 100% fresh because first time i installed emui 9 163 i came back a week later because of battery consuption that was way worse and real bad SOT
2- any reason not to use the easiest way ? why to prefer the complicated one : pulling the file from update.app and copy and etc....?
3- magisk modules will be usable ?
Thanks to those of you who will bring light or give me confident in re-installing pie.
And of course merry Christmas everyone
Click to expand...
Click to collapse
1. Steps is for rooting, if you wanna start fresh, you can consider wiping /data after update. So none of your previous mods data no cache will tag along to your EMUI 9
2. Reason is, the difference of firmware versioning betweem region. You told me you updated to .163. My prepatched ramdisk is from C636 .168, although most of the time it can work universally across region and version (just like how custom recovery work in a universal way), there's no telling what huawei actually did between version update. So its always best to use and patch your own file. Since it will give you confidence, its your own doing after all.
3. I use youtubevanced, LKT, systemless host, swap torpedo, busybox and detach magisk modules, all work just fine on EMUI 9. You only need to redownload and reinstall all the modules (if you didnt wipe data, like me), because installation from oreo version wont work straight away on EMUI 9.
for extra information, SafetyNet and MagiskHide all working as well. I can use my banking app just fine.
as for precaution info,
i suggest you to use the flashy tools to install EMUI 9 from PC instead of using HuRU,
i did the HuRU way, and ends up with a messed up software serial number and broken recovery partition, meaning i can't flash TWRP, stock recovery nor a patched recovery ramdisk to acquired root. It will all fall to an error screen, telling me no recovery image available inside the system, and ask me to update system again. Fortunately the phone still boot just fine to system.
scratched my heads for hours until i manage to resolved it by flashing Recovery META and Recovery Vendor image through fastboot. After that i can reflash stock recovery, and the patched one (after i confirm stock one work fine)

Thanks a lot for your answers.
---------- Post added at 06:42 PM ---------- Previous post was at 06:24 PM ----------
otonieru said:
1. Steps is for rooting, if you wanna start fresh, you can consider wiping /data after update. So none of your previous mods data no cache will tag along to your EMUI 9
Click to expand...
Click to collapse
One thing no clear to me is what i do of the magisk canary Zip file...?.... ? As twrp not working on emui 9...