Database Info

problem flashing 2.15 firmware.zip?

so i tried to flash the latest firmware. the commands i took were
adb reboot bootloader
fastboot oem rebootRUU
the last part is where im having problems. flashing the zip. i done 'fastboot flash zip firmware.zip'
i get the following. 'error: cannot load 'firmware.zip': Unknown error' any ideas? the zip file is in the same directory as fastboot

You renamed the file "firmware.zip" (no quotes) right? Or else changed the command syntax to match the actual file name (as its not actually "firmware.zip" when you download it).
And you are S-off?
If you can't get this way to work, you can try carl1861's flashable zip. It uses the AROMA installer, and you just flash from recovery:
http://forum.xda-developers.com/showthread.php?t=2331373

redpoint73 said:
You renamed the file "firmware.zip" (no quotes) right? Or else changed the command syntax to match the actual file name (as its not actually "firmware.zip" when you download it).
And you are S-off?
If you can't get this way to work, you can try carl1861's flashable zip. It uses the AROMA installer, and you just flash from recovery:
http://forum.xda-developers.com/showthread.php?t=2331373
Click to expand...
Click to collapse
I renamed the file from 2.15.0000...etc. to firmware.zip without quotes, and tried to fast boot flash and got the error I also tried flashing the file with the actual file name but no success!? the file is in the same directory as fastboot as it should be correct? And I'll check out carls tho thanks!
Sent from my HTC One XL using Tapatalk 4

I'll ask again, since you didn't answer: Are you s-off?
---------- Post added at 01:13 PM ---------- Previous post was at 01:12 PM ----------
696kris969 said:
the file is in the same directory as fastboot as it should be correct?
Click to expand...
Click to collapse
Yes, that is correct.

redpoint73 said:
I'll ask again, since you didn't answer: Are you s-off?
---------- Post added at 01:13 PM ---------- Previous post was at 01:12 PM ----------
Yes, that is correct.
Click to expand...
Click to collapse
Sorry yes I am s-off 2.14 firmware
Sent from my HTC One XL using Tapatalk 4

Is your device listed if you type the command:
fastboot devices

If you renamed the firmware zip file to firmware.zip then to flash it you would need to enter fastboot flash zip firmware.zip.zip because you have .zip at the end of the file name. Am I right? So try renaming the file without the .zip at the end.

Sluff said:
If you renamed the firmware zip file to firmware.zip then to flash it you would need to enter fastboot flash zip firmware.zip.zip because you have .zip at the end of the file name. Am I right?
Click to expand...
Click to collapse
Could be. OP should make sure he doesn't have the computer OS set to hide file extensions when he renamed the file. Similar mistakes have been made before.

deleted

Ok guys I'm gonna give sluffs advice a go I'll report back and yes my device is listed
edit: cheers sluff was trying to over thing something as simple
Sent from my HTC One XL using Tapatalk 4

How about carl1961's flashable zip? That should be pretty foolproof. If you are able to flash ROMs (and also S-off and SuperCID), you should be able to flash his firmware update zip.

Did my advice work for you? I'm glad you got it flashed, I know I was a bit confused while trying to flash it myself.

Sluff said:
If you renamed the firmware zip file to firmware.zip then to flash it you would need to enter fastboot flash zip firmware.zip.zip because you have .zip at the end of the file name. Am I right? So try renaming the file without the .zip at the end.
Click to expand...
Click to collapse
Its seeming more and more like this is the issue, as this person seems to have made the same goof: http://forum.xda-developers.com/showthread.php?p=45689800#post45689800
Although, I don't know why the OP hasn't tried the carl1961's version, flashable in recovery, as I suggested.

Can't OTA

Hi.
i tried to s-off my device, but no success :/
then recovered stock from twrp, after this i check OTA update and found OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401.6_release_383386.zip
did factory reset, flashed boot.img and recovery.img from this package: https://docs.google.com/file/d/0B1a-JXNXbe8wbkNxbnhncEZDdUU/edit?pli=1
tried to update, it,s failed.
my device:
tempered
relocked
s-on
h-boot 2.22
radio-1.24.40e.00.26
OS-3.10.401.6 (4.09.401.3)---> red color?????
eMMC-boot 1024MB
Jun 24 1014, 15:21:25.0
any help?
tried flash zip via fastboot oem rebootRUU
FAILED: (remote: 12 signature verify fail)

nicniewid said:
Hi.
i tried to s-off my device, but no success :/
then recovered stock from twrp, after this i check OTA update and found OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401.6_release_383386.zip
did factory reset, flashed boot.img and recovery.img from this package: https://docs.google.com/file/d/0B1a-JXNXbe8wbkNxbnhncEZDdUU/edit?pli=1
tried to update, it,s failed.
my device:
tempered
relocked
s-on
h-boot 2.22
radio-1.24.40e.00.26
OS-3.10.401.6 (4.09.401.3)---> red color?????
eMMC-boot 1024MB
Jun 24 1014, 15:21:25.0
any help?
tried flash zip via fastboot oem rebootRUU
FAILED: (remote: 12 signature verify fail)
Click to expand...
Click to collapse
im not sure but i think it failed because you didnt have s off when you tried to flash it

The OTA's will fail if you have changes files that the OTA wants to patch, or if those files are missing.
If you are purely stock (or odex stock root dump from somewhere) the update should work (it did for me at least).
Also, make sure you are on 3.10.401.6 (note the 6 at the end), there is a rom here somewhere with 3.10.401.4 which will not take the OTA towards 4.09.xxx.
The most likely files that are 'changed' on which the 4.09 OTA is failing, are the 'stock apps' that are on the _data_ partition (not /system). Since your /data partition is wiped when you htcdev-unlock, you lose some of the stock apps (like flashlight, sound recorder, etc..). Since this 4.09 OTA patches two of them, the OTA checks if the files are there and are still the same.
Take a look in the OTA package you had the recovery.img and boot.img from. You'll see there is a /data folder in it. Make sure the files in this folder are in your /data folder (you can use 'adb push' from TWRP, or place them on your internal storage and then move them over from TWRP if you know some linux cmdline commands). A root-file-explorer app can also work.
In a nutshell, take the /data/preload folder from the 3.10.401.6 OTA and make sure the files from there are in a /data/preload folder on your device. Then try the OTA towards 4.09.401 again.

dipje said:
The OTA's will fail if you have changes files that the OTA wants to patch, or if those files are missing.
If you are purely stock (or odex stock root dump from somewhere) the update should work (it did for me at least).
Also, make sure you are on 3.10.401.6 (note the 6 at the end), there is a rom here somewhere with 3.10.401.4 which will not take the OTA towards 4.09.xxx.
The most likely files that are 'changed' on which the 4.09 OTA is failing, are the 'stock apps' that are on the _data_ partition (not /system). Since your /data partition is wiped when you htcdev-unlock, you lose some of the stock apps (like flashlight, sound recorder, etc..). Since this 4.09 OTA patches two of them, the OTA checks if the files are there and are still the same.
Take a look in the OTA package you had the recovery.img and boot.img from. You'll see there is a /data folder in it. Make sure the files in this folder are in your /data folder (you can use 'adb push' from TWRP, or place them on your internal storage and then move them over from TWRP if you know some linux cmdline commands). A root-file-explorer app can also work.
In a nutshell, take the /data/preload folder from the 3.10.401.6 OTA and make sure the files from there are in a /data/preload folder on your device. Then try the OTA towards 4.09.401 again.
Click to expand...
Click to collapse
Everytfing works fine, i'm very thankful Do You know how to restore stock apps like flashlight or calc?

nicniewid said:
Everytfing works fine, i'm very thankful Do You know how to restore stock apps like flashlight or calc?
Click to expand...
Click to collapse
Depends for which ROM you are using now. There are some threads around, and you can find in them in _some_ of the OTA packages.
If you are on the latest 4.4.2 with Sense6, there is this thread: http://forum.xda-developers.com/showthread.php?t=2696399 but I have no clue if they work alright.
Also, if you download the OTA file from here (http://forum.xda-developers.com/showthread.php?t=2575766) inside that .zip file is a /data/preload folder which contains Calculator and Flashlight (and maybe some other needed files).
If you are on 4.3 with Sense 5.5, there is a link to the stock rom here (http://forum.xda-developers.com/showthread.php?t=2575766) that in the first post at the bottom has a Mega downlink link to 'the missing apps'.
The original files were in /data/preload on your device, and since doing the htcdev-unlock thing clears the entire /data, you will lose them. If you made a proper backup your original files maybe in there. Most OTA packages include these files as well, or maybe patches to the existing files (which are useless if you don't have the originals).
I gave some links by quickly searching, if you need more and for another version do please use the search function, they are around here.

Stock recovery and boot collection

In case, you want the stock boot/recovery to install Magisk like me, you can get it out of the firmware.zip inside the OTA zip, which you can download from HTC server using the link:
Taiwan model 1.10.709.23:
http://fotadl-az.htc.com/secure/OTA....05.709.12_release_517077z7dxrjhjj6rk2y9h.zip
Taiwan model 1.23.709.3:
http://fotadl-az.htc.com/secure/OTA....10.709.23_release_518569sr63mm3mtji85ret.zip
Hong Kong model 1.10.400.23
http://fotadl-az.htc.com/secure/OTA....05.400.13_release_517158ov5r8lbbi6tc9m38.zip
I have extracted the recovery.img and boot.img for Taiwan version. If someone doesn't want to extract it themselves, let me know through PM. I can send it to you.

devsk said:
In case, you want the stock boot/recovery to install Magisk like me, you can get it out of the firmware.zip inside the OTA zip, which you can download from HTC server using the link:
http://fotadl-az.htc.com/secure/OTA....05.709.12_release_517077z7dxrjhjj6rk2y9h.zip
I have extracted the recovery.img and boot.img. If someone doesn't want to extract it themselves, let me know through PM. I can send it to you.
Click to expand...
Click to collapse
Desk
Thank you your work .Is this version recovery work for HTC U 11 PLUS China. Mainland version 2Q4D200.THANK YOU again.

Would you know how to enable volte and wifi calling?

cameljockey1 said:
Would you know how to enable volte and wifi calling?
Click to expand...
Click to collapse
Not yet.

Perfectionalism said:
Desk
Thank you your work .Is this version recovery work for HTC U 11 PLUS China. Mainland version 2Q4D200.THANK YOU again.
Click to expand...
Click to collapse
I would like to know this too. I have the Chinese U11+ and I'm desperately looking for the boot.img and recovery.img for this variant (2Q4D200)
Thanks in advance!

Prot02018 said:
I would like to know this too. I have the Chinese U11+ and I'm desperately looking for the boot.img and recovery.img for this variant (2Q4D200)
Thanks in advance!
Click to expand...
Click to collapse
screenshot of your software information page in settings showing "Software number" (e.g. 1.10.709.23 for me, it would be 1.xx.1405.xx for you).

devsk said:
screenshot of your software information page in settings showing "Software number" (e.g. 1.10.709.23 for me, it would be 1.xx.1405.xx for you).
Click to expand...
Click to collapse
Here's the screenshots! Many thanks devsk.

Perfectionalism said:
Desk
Thank you your work .Is this version recovery work for HTC U 11 PLUS China. Mainland version 2Q4D200.THANK YOU again.
Click to expand...
Click to collapse
Prot02018 said:
I would like to know this too. I have the Chinese U11+ and I'm desperately looking for the boot.img and recovery.img for this variant (2Q4D200)
Thanks in advance!
Click to expand...
Click to collapse
OCEAN_M_DTWL
modelid: 2Q4D20000
cidnum: HTCCN701
OTA zip link (1.05.1405.16 - 1.03.1405.1)
https://drive.google.com/file/d/1Q3Kz88fJm1NA6ccPcb1jbQstZYWASnFO/view?usp=sharing

nenebear said:
OCEAN_M_DTWL
modelid: 2Q4D20000
cidnum: HTCCN701
OTA zip link (1.05.1405.16 - 1.03.1405.1)
https://drive.google.com/file/d/1Q3Kz88fJm1NA6ccPcb1jbQstZYWASnFO/view?usp=sharing
Click to expand...
Click to collapse
Thanks nenebear. Is this is the OTA file to go from stock 1.03.1405.1 to latest 1.05.1405.16 ?
I found the RUU's for the version of my phone also. Can anybody here confirm that the stock recovery zip file found at the following link will allow me to go back to stock recovery if I decide to flash TWRP?
https://androidfilehost.com/?w=search&s=OCEAN_M_DTWL
Thanks guys

Please help me!
I have unlocked my bootloader, installed twrp. Unfortunately, twrp is worthless since it can not be used as it seems...
Now I wonder if I can use this guide to root my phone:
"1. Download http://fotadl-az.htc.com/secure/OTA_...bbi6tc9m38.zip
Edit / Important: Read next post down below before Step 2/
2. Extract firmware.zip.
3. Extract boot.img from firmware.zip from step 2 and transfer to the /sdcard.
4. Install Magisk Manager and select Beta channel
5. Click install and choose to use "patch the stock boot image" method. It will browse you to /sdcard. Choose the boot.img from step 3. After its done, it will give you path of patched boot image.
6. Transfer the patched boot image from step 5 to PC using 'adb pull'
7. Boot the phone into download mode and flash the patched boot image.
8. Reboot and enjoy!!"
Where/how can I get the correct boot.img för my device?
My version is "1.10.401.23 9.0_g CL991677 release-keys" and none of the download links match my version? Or can I use some of them anyway?
I would be very happy and thanksful if I got help so I can get root access!
Best regards/ David

Davil_79 said:
Please help me!
I have unlocked my bootloader, installed twrp. Unfortunately, twrp is worthless since it can not be used as it seems...
Now I wonder if I can use this guide to root my phone:
"1. Download http://fotadl-az.htc.com/secure/OTA_...bbi6tc9m38.zip
Edit / Important: Read next post down below before Step 2/
2. Extract firmware.zip.
3. Extract boot.img from firmware.zip from step 2 and transfer to the /sdcard.
4. Install Magisk Manager and select Beta channel
5. Click install and choose to use "patch the stock boot image" method. It will browse you to /sdcard. Choose the boot.img from step 3. After its done, it will give you path of patched boot image.
6. Transfer the patched boot image from step 5 to PC using 'adb pull'
7. Boot the phone into download mode and flash the patched boot image.
8. Reboot and enjoy!!"
Where/how can I get the correct boot.img för my device?
My version is "1.10.401.23 9.0_g CL991677 release-keys" and none of the download links match my version? Or can I use some of them anyway?
I would be very happy and thanksful if I got help so I can get root access!
Best regards/ David
Click to expand...
Click to collapse
I think yours is the Europe model. If so, download the following ZIP:
https://androidfilehost.com/?fid=889964283620770441
Extract firmware.zip from it, and you will then extract boot.img from the firmware.zip, and then, patch that in magisk manager. Hope that helps!

devsk said:
I think yours is the Europe model. If so, download the following ZIP:
https://androidfilehost.com/?fid=889964283620770441
Extract firmware.zip from it, and you will then extract boot.img from the firmware.zip, and then, patch that in magisk manager. Hope that helps!
Click to expand...
Click to collapse
Many thanks!
I should have a European model. If I'm looking in the Download mode:
"htc_ocmdugl PVT S-ON
LK-1.0.0.0000
RADIO 8998-002772-1711021849
OpenDSP-UNKNOWN
OS 1.10.401.23
Nov 25 2017.01: 13: 33 (991677)"
If something goes wrong, or if it would be the wrong boot.img, can I flash a complete RUU via adb fastboat so I dont brick my phone?

Davil_79 said:
Many thanks!
I should have a European model. If I'm looking in the Download mode:
"htc_ocmdugl PVT S-ON
LK-1.0.0.0000
RADIO 8998-002772-1711021849
OpenDSP-UNKNOWN
OS 1.10.401.23
Nov 25 2017.01: 13: 33 (991677)"
If something goes wrong, or if it would be the wrong boot.img, can I flash a complete RUU via adb fastboat so I dont brick my phone?
Click to expand...
Click to collapse
That link matches your version exactly. You should be good with boot.img from that ZIP. Make backup of your stuff and be very careful with commands you fire...

devsk said:
That link matches your version exactly. You should be good with boot.img from that ZIP. Make backup of your stuff and be very careful with commands you fire...
Click to expand...
Click to collapse
Hmm.. It is 25 pcs. compressed zip-files in this download.
In one of the zip there is "boot_signed.img"
It must be it. But when I try to unzip it doesn't work. It says the file is corrupt [emoji852]️.
I will try to download the file again, mayby the download failed.
Edit: The file is corrupt. I cant unzip it
Skickat från min HTC U11 plus via Tapatalk

Davil_79 said:
Hmm.. It is 25 pcs. compressed zip-files in this download.
In one of the zip there is "boot_signed.img"
It must be it. But when I try to unzip it doesn't work. It says the file is corrupt [emoji852]️.
I will try to download the file again, mayby the download failed.
Edit: The file is corrupt. I cant unzip it
Skickat från min HTC U11 plus via Tapatalk
Click to expand...
Click to collapse
You need RUU decrypt tool to retrieve the boot and recovery image

Root HTC U11+ European model software number 1.10.401.23
To root your HTC U11+ thru twrp use version 3.2.0.0
1. make sure you got Magisk-15.2 on you sd-card
2. boot into TWRP and leave system read only
3.goto install and install Magisk (in my case 15.2)
4. you will get error, like "can't mount data" (not to worry)
5. after install GO BACK!! DO NOT REBOOT!!
6. format data AND THEN reboot!!
7 You'll have to setup your phone as a new one; finish that and install Magisk_Manager
8 your now rooted!!! check with root checker
Hope this will help you;
Davil_79 said:
Please help me!
I have unlocked my bootloader, installed twrp. Unfortunately, twrp is worthless since it can not be used as it seems...
Now I wonder if I can use this guide to root my phone:
"1. Download http://fotadl-az.htc.com/secure/OTA_...bbi6tc9m38.zip
Edit / Important: Read next post down below before Step 2/
2. Extract firmware.zip.
3. Extract boot.img from firmware.zip from step 2 and transfer to the /sdcard.
4. Install Magisk Manager and select Beta channel
5. Click install and choose to use "patch the stock boot image" method. It will browse you to /sdcard. Choose the boot.img from step 3. After its done, it will give you path of patched boot image.
6. Transfer the patched boot image from step 5 to PC using 'adb pull'
7. Boot the phone into download mode and flash the patched boot image.
8. Reboot and enjoy!!"
Where/how can I get the correct boot.img för my device?
My version is "1.10.401.23 9.0_g CL991677 release-keys" and none of the download links match my version? Or can I use some of them anyway?
I would be very happy and thanksful if I got help so I can get root access!
Best regards/ David
Click to expand...
Click to collapse

bnwg said:
You need RUU decrypt tool to retrieve the boot and recovery image
Click to expand...
Click to collapse
Aha! Hm ok So it wasnt that easy. I am such a Noob .
I have never used that RUU decrypt tool and it seems a bit complicated but I have to try.
Thanks for your answer!
---------- Post added at 04:22 PM ---------- Previous post was at 04:12 PM ----------
freebsd124 said:
To root your HTC U11+ thru twrp use version 3.2.0.0
1. make sure you got Magisk-15.2 on you sd-card
2. boot into TWRP and leave system read only
3.goto install and install Magisk (in my case 15.2)
4. you will get error, like "can't mount data" (not to worry)
5. after install GO BACK!! DO NOT REBOOT!!
6. format data AND THEN reboot!!
7 You'll have to setup your phone as a new one; finish that and install Magisk_Manager
8 your now rooted!!! check with root checker
Hope this will help you;
Click to expand...
Click to collapse
Thank you! I will try this!
I'm considering starting a new thread. I know there are more people who have similar problems and considerations within this.

HTC-RUU-Decrypt_Tool
You'll find the htc-ruu_decrypt-tool here
Davil_79 said:
Aha! Hm ok So it wasnt that easy. I am such a Noob .
I have never used that RUU decrypt tool and it seems a bit complicated but I have to try.
Thanks for your answer!
---------- Post added at 04:22 PM ---------- Previous post was at 04:12 PM ----------
Thank you! I will try this!
I'm considering starting a new thread. I know there are more people who have similar problems and considerations within this.
Click to expand...
Click to collapse

freebsd124 said:
To root your HTC U11+ thru twrp use version 3.2.0.0
1. make sure you got Magisk-15.2 on you sd-card
2. boot into TWRP and leave system read only
3.goto install and install Magisk (in my case 15.2)
4. you will get error, like "can't mount data" (not to worry)
5. after install GO BACK!! DO NOT REBOOT!!
6. format data AND THEN reboot!!
7 You'll have to setup your phone as a new one; finish that and install Magisk_Manager
8 your now rooted!!! check with root checker
Hope this will help you;
Click to expand...
Click to collapse
YES! Root access :good: Finaly a success! :victory:
Now my phone is like I want it to be!! Thank you so much!!'

If it's useful for somebody wanting to try twrp and/or custom kernel...you can find inside stock boot and recovery for India/HK version, 1.10.400.23 and the new 1.24.400.2
https://drive.google.com/file/d/18FgmqIb_4UNpmRsXyxKj2bbCf6TnTXSd/view?usp=sharing

OTA Update without loosing root and wiping data possible?

I rooted my HTC U11+ using Magisk without having TWRP installed. I can't find the link anymore, but I think it was through fastboot and if I remember correctly, I had to format /data after installing Magisk due to the device encryption. Everything is working fine.
Today I got a notification that a new firmware with the version number 1.24.401.2 is available (current version is 1.10.401.23). I'm pretty sure if I install it, i I will loose root and I would have to install Magisk again to gain root back which would require to format /data. I would like to prevent that since I've spend ages to configure and adjusting everything to my needs and I'm not keen to do that again.
Is there a way of installing the OTA update without loosing root and having to wipe /data?

midiwidi said:
I rooted my HTC U11+ using Magisk without having TWRP installed. I can't find the link anymore, but I think it was through fastboot and if I remember correctly, I had to format /data after installing Magisk due to the device encryption. Everything is working fine.
Today I got a notification that a new firmware with the version number 1.24.401.2 is available (current version is 1.10.401.23). I'm pretty sure if I install it, i I will loose root and I would have to install Magisk again to gain root back which would require to format /data. I would like to prevent that since I've spend ages to configure and adjusting everything to my needs and I'm not keen to do that again.
Is there a way of installing the OTA update without loosing root and having to wipe /data?
Click to expand...
Click to collapse
Would the following be helpful?
Haven't tried myself yet.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

Thank you for the link DanteGR. It looks promising.
I'll have to find out if my HTC U11+ is supported by FlashFire. It most likely doesn't have two partitions (A/B).
So if somebody knows if the U11+ is working with FlashFire, please let me know!
Is there a way of backing everything up in case something goes wrong with with the OTA update using FlashFire? I'm not keen on loosing all the adjustments and settings I made in the last couple of weeks (I even modified files in /data/data to fix App issues). As far as i know Nandroid backups are not possible because the currently available TWRP recovery for the U11+ doesn't support data decryption. I have backups to Google Drive enabled (with all options including App data), but I don't know if that is enough to bring the system back into the current state afterwards.

midiwidi said:
Thank you for the link DanteGR. It looks promising.
I'll have to find out if my HTC U11+ is supported by FlashFire. It most likely doesn't have two partitions (A/B).
So if somebody knows if the U11+ is working with FlashFire, please let me know!
Is there a way of backing everything up in case something goes wrong with with the OTA update using FlashFire? I'm not keen on loosing all the adjustments and settings I made in the last couple of weeks (I even modified files in /data/data to fix App issues). As far as i know Nandroid backups are not possible because the currently available TWRP recovery for the U11+ doesn't support data decryption. I have backups to Google Drive enabled (with all options including App data), but I don't know if that is enough to bring the system back into the current state afterwards.
Click to expand...
Click to collapse
No problem.
AFAIK unfortunately there isn't a way for a full backup without a completely functioning TWRP.
If rooted, Titanium would be your best bet but not for everything obviously.

midiwidi said:
I rooted my HTC U11+ using Magisk without having TWRP installed. I can't find the link anymore, but I think it was through fastboot and if I remember correctly, I had to format /data after installing Magisk due to the device encryption. Everything is working fine.
Today I got a notification that a new firmware with the version number 1.24.401.2 is available (current version is 1.10.401.23). I'm pretty sure if I install it, i I will loose root and I would have to install Magisk again to gain root back which would require to format /data. I would like to prevent that since I've spend ages to configure and adjusting everything to my needs and I'm not keen to do that again.
Is there a way of installing the OTA update without loosing root and having to wipe /data?
Click to expand...
Click to collapse
As you, I have root but no TWRP installed. I did the OTA update and I didn't lost my data. I lost root during the process but it was very easy to install it back without loosing or wipe data.
If you have installed Magisk via patched boot.img, here is what I have done :
-Go in Magisk, choose uninstall and then "restore image"
-Then, go check for update on your phone and start it.
-At the same time, download stock RUU rom (the same as the OTA, here for European version : https://forum.xda-developers.com/htc-u11/development/htc-u11-stock-rom-ruu-t3741849) and extract boot.img from it with RUUdecrypttool (https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928). It can be long.
-When update is complete and you have extracted boot.img, put it in your phone and patch it with magisk : install, patch boot image. Then you will have a "patched_boot.img" in your magiskmanager folder. Copy this file on your PC.
-Go to download mode on your phone and flash patched_boot.img via Flashtool.
Root is back, no data lost :good:

Kidy973 said:
As you, I have root but no TWRP installed. I did the OTA update and I didn't lost my data. I lost root during the process but it was very easy to install it back without loosing or wipe data.
If you have installed Magisk via patched boot.img, here is what I have done :
-Go in Magisk, choose uninstall and then "restore image"
-Then, go check for update on your phone and start it.
-At the same time, download stock RUU rom (the same as the OTA, here for European version : https://forum.xda-developers.com/htc-u11/development/htc-u11-stock-rom-ruu-t3741849) and extract boot.img from it with RUUdecrypttool (https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928). It can be long.
-When update is complete and you have extracted boot.img, put it in your phone and patch it with magisk : install, patch boot image. Then you will have a "patched_boot.img" in your magiskmanager folder. Copy this file on your PC.
-Go to download mode on your phone and flash patched_boot.img via Flashtool.
Root is back, no data lost :good:
Click to expand...
Click to collapse
Just a heads up.
I think for OTAs only (NOT RUUs) you don't even have to use the decrypt tool.
The zip is already decrypted so just extract the boot.img.
EDIT: Not 100% sure though will try it out this evening.

DanteGR said:
Just a heads up.
I think for OTAs only (NOT RUUs) you don't even have to use the decrypt tool.
The zip is already decrypted so just extract the boot.img.
EDIT: Not 100% sure though will try it out this evening.
Click to expand...
Click to collapse
That is correct.
I have done it many times.

m3johan said:
That is correct.
I have done it many times.
Click to expand...
Click to collapse
Oh well.
Last night I downloaded a random OTA for the HK version and the firmware.zip inside it could not be opened I guess due to encryption.
Are you sure about that?

DanteGR said:
Oh well.
Last night I downloaded a random OTA for the HK version and the firmware.zip inside it could not be opened I guess due to encryption.
Are you sure about that?
Click to expand...
Click to collapse
I can not be 100% sure, but all I have unpacked including this 1.24.401.2 ota were no problem.
Can you give me the link to the HK-ota?

m3johan said:
I can not be 100% sure, but all I have unpacked including this 1.24.401.2 ota were no problem.
Can you give me the link to the HK-ota?
Click to expand...
Click to collapse
This is the one I tried to extract without success.
Just to make it clear. I had no problem extracting the actual OTA. The problem was trying to extract the firmware.zip inside it.
Thank you for your input.
https://www.androidfilehost.com/?fid=962187416754455026

DanteGR said:
This is the one I tried to extract without success.
Just to make it clear. I had no problem extracting the actual OTA. The problem was trying to extract the firmware.zip inside it.
Thank you for your input.
https://www.androidfilehost.com/?fid=962187416754455026
Click to expand...
Click to collapse
You are right. I could not unpack firmware from that one either.

Deleted

m3johan said:
You are right. I could not unpack firmware from that one either.
Click to expand...
Click to collapse
The decrypt tool doesn't seem too bad after all though.
I'll have to try it shortly.

For those who are using Taiwan model, what is your software number?
Mine is 1.23.709.9

RUU decrypt tool
DanteGR said:
The decrypt tool doesn't seem too bad after all though.
I'll have to try it shortly.
Click to expand...
Click to collapse
RUU_decrypt_tool works like a charm
the command on the command line is (in windows) RUU_decrypt_tool -f RUU file name (use TAB for name completion or rename to RUU.zip) (for firmware files) which gets you (see thumbnail)
The tool automatically has a output as "OUT" in the folder where it resides; I've put my RUU file in the ADB folder together wit the RUU_decrypt_tool
You'll find the RUU_decrypt_tool here
btw: I am 70 years young, so if I can do it most people can as well.....
If none of the required arguments are supplied a simple Yes/No interface will be presented.
Required arguments (and/or):
-s, --system extract the system.img and boot.img (for ROM)
-f, --firmware extract the firmware files
-z, --sdruuzip copy and rename rom.zip for SD-Card flashing
Note: this will create a duplicate if the input is already a rom.zip
Keyfile Updater arguments:
-o, --offline disable down/upload of keyfiles
--no-upload do not upload if a new keyfile is generated
--sync-keyfiles sync entire keyfile folder (download & upload)
when used without a RUU the tool will only synchronize the
keyfiles, otherwise it will download new keyfiles before decrypting
and upload only if a new keyfile is generated
Click to expand...
Click to collapse

When I used to have htc 10 s-on I could update the fw using a zip file(perhaps firmware. Zip) inside the OTA file for my cid and flash it in RUU mode, of course I had to use a custom rom based on the same fw to complete it

Finally, after a couple of month and being annoyed of the update message popping up all the time, I got some time to proceed with the update.
I found that what I've said in my first post isn't true. I had a non-official TWRP (without decryption support) installed and now remember that I have installed Magisk through that.
I've started the update procedure with clicking "uninstall" and "restore image" in the Magisk app. After downloading the OTA, I clicked on install now. My phone rebooted into recovery (TWRP) and prompted to enter my unlocking pattern. I entered it, but TWRP said something like can't mount, wrong password.
I thought it's because TWRP doesn't support decryption yet and I need to go back to the stock recovery to be able to apply the OTA. I extracted the recovery_signed.img from here (from the same software version I'm currently running 1.10.401.23) and flashed it using fastboot. If I boot into recovery now, I see it's the stock one, but it shows a red exclamation mark in a red triangle. I can press power button + volume up and get into the normal recovery menu. I've tried to wipe the cache there, but it didn't made a difference. I still get that red exclamation mark. If I download the OTA and click on install now, my phone restarts and shows the normal picture of applying the update until about 24% of progress and then it shows the red exclamation mark again. If I press power + volume up now, nothing happens.
If I manually boot into recovery and use power + volume up to get into the recovery menu, there are two options to apply an update. One using the sdcard and one using ADB. I have the hope that the red exclamation mark is gone once I installed the update manually.
The sdcard option doesn't work. The recovery shows the message can't mount /sdcard. The ADB sideload option causes problems too.
If I use a older version of ADB I get the error "cannot read OTA.zip" in my command window on the PC. I've tried it with a small text file and that worked. I read that it has something to do with the address space which is too small and that I should use the newest version from googles platform tools. I installed version 27.0.1 and used the contained ADB to do the sideload. This time I got an error message like "adb server version (31) doesn't match this client (36)", but it didn't say that it can't read the file.
I'm kind of stuck now. Has somebody a suggestion how to proceed, to get rid of the red exclamation mark so that I can normally apply the OTA update and gain root again afterwards by flashing a Magisk patched boot.img through fastboot?

midiwidi said:
...shows the normal picture of applying the update until about 24% of progress and then it shows the red exclamation mark again....
Click to expand...
Click to collapse
You have a modified /system partition. You will need to restore stock system partition of the version you are running to get past this.

You have a modified /system partition. You will need to restore stock system partition of the version you are running to get past this.
Click to expand...
Click to collapse
Thank you very much for this hint. I will do a
fastboot flash system system.img
tonight and let you know how it went.

I did flash the original system.img. Here the output of the command window
C:\Users\midiwidi\Downloads\HTC_U11+\Original_HTC_Firmware_Europe\OUT_2Q4D_1.10.401.23\system>fastboot.exe flash system system.img
sending 'system' (16384 KB)...
OKAY [ 1.651s]
writing 'system'...
(bootloader) HOSD CL#991677
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.461s]
finished. total time: 5.111s
Unfortunately that didn't change anything. I still get the red exclamation mark if I boot into recovery
{
"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"
}
.
Is there a log file or something similar to find out what the recovery is complaining about? This is the output after bypassing the red exclamation mark with power + volume up
.
Any other ideas how to proceed?

GIONEE A1 PLUS Custom Recovery Needed Urgently

Please someone should help me with custom recovery for Gionee A1 Plus, I can provide the stock recovery.. Or if anyone can provide general Stock with Root Access so I can flash my phone with it.. I just need help.. My Airtime keeps depleting for no reason..

https://forum.xda-developers.com/showthread.php?t=1943625

Please just help me out
Thanks but can you help me.. reading through this can cause headache.. I am not trying to be lazy, just too complicated. thank you
DSA said:
https://forum.xda-developers.com/showthread.php?t=1943625
Click to expand...
Click to collapse

First of all there is no stable custom recovery for this phone (due to its less popularity) so don't expect a support.
Secondly don't try to code it on your own because it's bit complicated and chances to make a suitable recovery are low.
Now I have a solution for you and it's not that complicated, it will provide root and a (partially working CWM recovery)
1st step : On your computer extract "BOOT.IMG" and scatter files from your rom (if you don't have so go download the same rom you're using and extract the specific file mentioned) and copy paste it in your phone directory. Then download & install Magisk manager on your phone.
2nd step : Open Magisk app, download patch [I believe its root files] or something like that then apply it on the "BOOT.IMG" file that you just transferred it on your phone [must remember the file directory you selected].
3rd step : go back to your computer and retrieve the patched or modded "BOOT.IMG" file, it must be in "Phone directory\Magisk" folder [it may not be the one you transferred earlier], now turn your phone off, flash your phones' "Boot partition" with the this patched file using SP FLASHTOOL and original scatter file so you can get the #ROOT privileges after you turn on your phone.
(Remember to leave other partitions unchecked Before start flashing).
And finally, on your phone download & install Flashify app and give it SU permission from Magisk and select The the custom recovery IMG file, the one which will provided in end of article, then of course flash it and reboot your phone.
~ This Philz CWM custom recovery is partially working or in other words it still on alpha stage.
Link : https://mega.nz/#!wSJ1nRbI!gWJ0wSi_AmxBx9Cj_Oa7XCsTR0hl3xJWAgDf5SyUYT8
Sent from my Condor M1 Plus using Tapatalk

Thanks! I am trying to check it out
Thanks bro, I will write you back soon, let me quickly get to work on this, hopefully, it will work.
The Mega link you sent, is it a custom recovery I could try out as well without going through the magicdsk steps?
Please advise
sonicswink said:
First of all there is no stable custom recovery for this phone (due to its less popularity) so don't expect a support.
Secondly don't try to code it on your own because it's bit complicated and chances to make a suitable recovery are low.
Now I have a solution for you and it's not that complicated, it will provide root and a (partially working CWM recovery)
1st step : On your computer extract "BOOT.IMG" and scatter files from your rom (if you don't have so go download the same rom you're using and extract the specific file mentioned) and copy paste it in your phone directory. Then download & install Magisk manager on your phone.
2nd step : Open Magisk app, download patch [I believe its root files] or something like that then apply it on the "BOOT.IMG" file that you just transferred it on your phone [must remember the file directory you selected].
3rd step : go back to your computer and retrieve the patched or modded "BOOT.IMG" file, it must be in "Phone directory\Magisk" folder [it may not be the one you transferred earlier], now turn your phone off, flash your phones' "Boot partition" with the this patched file using SP FLASHTOOL and original scatter file so you can get the #ROOT privileges after you turn on your phone.
(Remember to leave other partitions unchecked Before start flashing).
And finally, on your phone download & install Flashify app and give it SU permission from Magisk and select The the custom recovery IMG file, the one which will provided in end of article, then of course flash it and reboot your phone.
~ This Philz CWM custom recovery is partially working or in other words it still on alpha stage.
Link : https://mega.nz/#!wSJ1nRbI!gWJ0wSi_AmxBx9Cj_Oa7XCsTR0hl3xJWAgDf5SyUYT8
Sent from my Condor M1 Plus using Tapatalk
Click to expand...
Click to collapse

After installing Philz recovery, it keeps entering recovery.. Help!
I tried this link Link : https://mega.nz/#!wSJ1nRbI!gWJ0wSi_A...xJWAgDf5SyUYT8, it made my phone restart at the logo stage. I guess the custom recovery is not compatible. I have now done fresh installing of my rom twice now.
Meanwhile, I followed a download on how to create my Philz custom recovery, it installed but after installing supersu.zip, it keep loading to recovery without entering phone. Please help!
sonicswink said:
First of all there is no stable custom recovery for this phone (due to its less popularity) so don't expect a support.
Secondly don't try to code it on your own because it's bit complicated and chances to make a suitable recovery are low.
Now I have a solution for you and it's not that complicated, it will provide root and a (partially working CWM recovery)
1st step : On your computer extract "BOOT.IMG" and scatter files from your rom (if you don't have so go download the same rom you're using and extract the specific file mentioned) and copy paste it in your phone directory. Then download & install Magisk manager on your phone.
2nd step : Open Magisk app, download patch [I believe its root files] or something like that then apply it on the "BOOT.IMG" file that you just transferred it on your phone [must remember the file directory you selected].
3rd step : go back to your computer and retrieve the patched or modded "BOOT.IMG" file, it must be in "Phone directory\Magisk" folder [it may not be the one you transferred earlier], now turn your phone off, flash your phones' "Boot partition" with the this patched file using SP FLASHTOOL and original scatter file so you can get the #ROOT privileges after you turn on your phone.
(Remember to leave other partitions unchecked Before start flashing).
And finally, on your phone download & install Flashify app and give it SU permission from Magisk and select The the custom recovery IMG file, the one which will provided in end of article, then of course flash it and reboot your phone.
~ This Philz CWM custom recovery is partially working or in other words it still on alpha stage.
Link : https://mega.nz/#!wSJ1nRbI!gWJ0wSi_AmxBx9Cj_Oa7XCsTR0hl3xJWAgDf5SyUYT8
Sent from my Condor M1 Plus using Tapatalk
Click to expand...
Click to collapse

Yes me too I experienced bootloop but it's alright, sometimes it keep rebooting for 5 ~ 10 mins before initializing system.
And SuperSU never worked for me, I guess it's Android 7.0 Nougat Magisk should more compatible.
Sent from my Allure M1 Plus using Tapatalk
---------- Post added at 05:03 PM ---------- Previous post was at 04:59 PM ----------
Magisk steps are for patching BOOT.IMG to gain root, unlike The custom recovery has philz cwm recovery.img you should try flashing it as is.
Sent from my Allure M1 Plus using Tapatalk

Help
Wow! you mean I should allow it boot for close to 30 minutes? and what will happen after that is done? please let me know... I have decided not to root anymore as I am very tired already.
The option you gave for me to root using magisk through boot.img did not work.. I tried installing many times but nothing shows up neither did I see any patch as well..
Please let me know if I need to let it reboot for 10 minutes or more if thats the solution then I will wait..
sonicswink said:
Yes me too I experienced bootloop but it's alright, sometimes it keep rebooting for 5 ~ 10 mins before initializing system.
And SuperSU never worked for me, I guess it's Android 7.0 Nougat Magisk should more compatible.
Sent from my Allure M1 Plus using Tapatalk
---------- Post added at 05:03 PM ---------- Previous post was at 04:59 PM ----------
Magisk steps are for patching BOOT.IMG to gain root, unlike The custom recovery has philz cwm recovery.img you should try flashing it as is.
Sent from my Allure M1 Plus using Tapatalk
Click to expand...
Click to collapse

It's a bit challenging task huh ?
Okay did you extracted the file BOOT.IMG from your Rom and patched it in Magisk as I said ?
Because that's the most important step.
samosward said:
Wow! you mean I should allow it boot for close to 30 minutes? and what will happen after that is done? please let me know... I have decided not to root anymore as I am very tired already.
The option you gave for me to root using magisk through boot.img did not work.. I tried installing many times but nothing shows up neither did I see any patch as well..
Please let me know if I need to let it reboot for 10 minutes or more if thats the solution then I will wait..
Click to expand...
Click to collapse
Sent from my Allure M1 Plus using Tapatalk
---------- Post added at 06:37 PM ---------- Previous post was at 06:27 PM ----------
After that you should see the patched file on output folder. This file flash it using sp flashtool and once the flash finishes launch Magisk app and you will see the ROOT access enabled.
It's a piece of cake boy.
Sent from my Allure M1 Plus using Tapatalk

Please disregard in earlier message, I have finally done the boot patching with magisk. I tried flashing just the patch_boot.img which I renamed to boot.img but it shows error message C0030004 on SPtools.. Do you recommend I flash the whole phone while I used the new boot.img instead of the stock boot.img? If you can write me soon I will appreciate it.
sonicswink said:
It's a bit challenging task huh ?
Okay did you extracted the file BOOT.IMG from your Rom and patched it in Magisk as I said ?
Because that's the most important step.
Sent from my Allure M1 Plus using Tapatalk
---------- Post added at 06:37 PM ---------- Previous post was at 06:27 PM ----------
After that you should see the patched file on output folder. This file flash it using sp flashtool and once the flash finishes launch Magisk app and you will see the ROOT access enabled.
It's a piece of cake boy.
Sent from my Allure M1 Plus using Tapatalk
Click to expand...
Click to collapse

It's done!
I have rooted my phone! I truly can't say how I did it but I think your advise helped me out by using Magisk Boot patch... wow! I am the most happiest at this time.. Thanks for your support, I appreciate!
samosward said:
Please disregard in earlier message, I have finally done the boot patching with magisk. I tried flashing just the patch_boot.img which I renamed to boot.img but it shows error message C0030004 on SPtools.. Do you recommend I flash the whole phone while I used the new boot.img instead of the stock boot.img? If you can write me soon I will appreciate it.
Click to expand...
Click to collapse

Glad you did it.
I recommend you to make a backup If you're inexperienced with Root risks management.
Sent from my Allure M1 Plus using Tapatalk

Yeah, I have my firmware backup, if anything goes wrong, I would reflash my phone but for now, I would keep using it like this. Although, Fingerprint is presently not working.. I guess it hs something to do with magisk...
sonicswink said:
Glad you did it.
I recommend you to make a backup If you're inexperienced with Root risks management.
Sent from my Allure M1 Plus using Tapatalk
Click to expand...
Click to collapse

Honestly I don't advice you to depend on a firmware backup in case of loss of system or software disfonctionnement.
If you are an advanced or experienced user, go ahead, if not then read this immediately :
Your phone has not Snapdragon chip, your phone is powered by Mediatek chipset.
You don't want to end up using your phone as 6 inches mp4 player or WiFi tablet after flashing.
Every MediaTek phone has a unique data in a partition called "NVRAM" "MODEM" or "BASEBAND" name differs for every brand. If you my friend will perform a flash from a downloaded firmware backup, this flash is going format or erase system (the partition you want to flash) plus all other partitions that hold the unique data files, so you'll definitely lose your phone's IMEI, WiFi MAC address, Bluetooth address, and all radio drivers.
Consider this a friendly advice that saves you a 200$ phone.
Sent from my Allure M1 Plus using Tapatalk

sonicswink said:
Honestly I don't advice you to depend on a firmware backup in case of loss of system or software disfonctionnement.
If you are an advanced or experienced user, go ahead, if not then read this immediately :
Your phone has not Snapdragon chip, your phone is powered by Mediatek chipset.
You don't want to end up using your phone as 6 inches mp4 player or WiFi tablet after flashing.
Every MediaTek phone has a unique data in a partition called "NVRAM" "MODEM" or "BASEBAND" name differs for every brand. If you my friend will perform a flash from a downloaded firmware backup, this flash is going format or erase system (the partition you want to flash) plus all other partitions that hold the unique data files, so you'll definitely lose your phone's IMEI, WiFi MAC address, Bluetooth address, and all radio drivers.
Consider this a friendly advice that saves you a 200$ phone.
Click to expand...
Click to collapse
So how can one avoid that on an mtk device? I have had that happen to me before. All the other can be sorted but i failed to resolve meid to the way it was.

Thanks for the advise bro but I am not an outright novice, even if anything goes wrong,
I can always flash imei, mac or Bluetooth ID to the phone anytime.
Just my fingerprint that isn't working is my issue presently, secondly, how can I get or update my firmware to the latest update for Android 7.0, this particular one seems to load/open almost everything slowly compared to the stock firmware that came with it.
sonicswink said:
Honestly I don't advice you to depend on a firmware backup in case of loss of system or software disfonctionnement.
If you are an advanced or experienced user, go ahead, if not then read this immediately :
Your phone has not Snapdragon chip, your phone is powered by Mediatek chipset.
You don't want to end up using your phone as 6 inches mp4 player or WiFi tablet after flashing.
Every MediaTek phone has a unique data in a partition called "NVRAM" "MODEM" or "BASEBAND" name differs for every brand. If you my friend will perform a flash from a downloaded firmware backup, this flash is going format or erase system (the partition you want to flash) plus all other partitions that hold the unique data files, so you'll definitely lose your phone's IMEI, WiFi MAC address, Bluetooth address, and all radio drivers.
Consider this a friendly advice that saves you a 200$ phone.
Sent from my Allure M1 Plus using Tapatalk
Click to expand...
Click to collapse

tonde4jc said:
So how can one avoid that on an mtk device? I have had that happen to me before. All the other can be sorted but i failed to resolve meid to the way it was.
Click to expand...
Click to collapse
Just perform a Nandroid backup of indicated partitions and partitions you want yo keep, then restore Nand backup after flash, or if you're not in position to make a backup, simply restore your phone with flashing selected system and storage partitions and avoid (uncheck) indicated partitions.
Sent from my Allure M1 Plus using Tapatalk
---------- Post added at 05:09 PM ---------- Previous post was at 04:31 PM ----------
samosward said:
Thanks for the advise bro but I am not an outright novice, even if anything goes wrong,
I can always flash imei, mac or Bluetooth ID to the phone anytime.
Just my fingerprint that isn't working is my issue presently, secondly, how can I get or update my firmware to the latest update for Android 7.0, this particular one seems to load/open almost everything slowly compared to the stock firmware that came with it.
Click to expand...
Click to collapse
I didn't say you're novice, but you are writing like one bro.
First after Root installation process is finished, you can forget about updates for two reasons :
1- Updates kills Root and any system mods.
~After update process don't expect to find any Root.
2- updates makes Root installation harder by fixing system bugs and updates Android security patch.
~After updates expect a harder root setup process and less convenient Root usage, lags and bugs in your device usage because of security conflicts. Because some of Root apps are considered as threat or hostile by Google.
One of the bugs or conflicts are the fingerprint disfonctionnement, and I've done some researches so I found the easiest and only way to safely use root without any security conflicts is to downgrade the initial Nougat 7.0 update of your phone, I believe there are other methods to fix this issue without downgrading but they are not a permanent solutions.
My phone is rooted and works well in this version.
Sent from my Allure M1 Plus using Tapatalk

The version I use.
{
"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 Allure M1 Plus using Tapatalk

Android Security patch level
April 5, 2017
Same Kernel 4.4.15
but my build is just too old
(SW Version)
A1 Plus_0301_V5242
(HW Version)
A1 Plus_Mainboard_P3
(hardware Vesion)
P3
My SW Version is just too old why my phone is moving too sluggishly, I am so so sure of that.
sonicswink said:
The version I use.View attachment 4589105
Sent from my Allure M1 Plus using Tapatalk
Click to expand...
Click to collapse

samosward said:
Android Security patch level
April 5, 2017
Same Kernel 4.4.15
but my build is just too old
(SW Version)
A1 Plus_0301_V5242
(HW Version)
A1 Plus_Mainboard_P3
(hardware Vesion)
P3
My SW Version is just too old why my phone is moving too sluggishly, I am so so sure of that.
Click to expand...
Click to collapse
Yes judging your device by the version infos you provided, it's very outdated, outdated Amigo UI firmwares are laggy and slow in response regardless to the hardware capacity.
Sent from my Allure M1 Plus using Tapatalk