Database Info

Upgrade QiKU (CP8692_I02) to 6.0.1, official updates and also activate VoLTE

Hello Friends
A little background first !!
QiKU Q Terra (CP8692_I02) which was sold in India and came pre-installed with 360 OS v21, Android 5.1. The OEM went back to China hence there haven not been any software update for our device. I had been trying to boot latest Chinese 360 OS on Indian Qiku Terra to get updates but after flashing the Chinese version the device would not boot at all and would get stuck in fastboot mode. To revive the device, I had to flash back the V21, I had tried several times but no success.
I even got in touch with the 360 OS engineers over mail with the help of an administrator of Qiku Chinese forum but the engineers said it's not possible to flash Chinese 360 OS on Indian Qiku Q Terra.
I had also been trying to root QiKU and I was able to figure it out all recently.
Check out my post -- https://forum.xda-developers.com/an...i02-unlock-t3493636/post69455878#post69455878
This tutorial is also useful for users of CP8692_M02 who had flashed the v21 on their devices and now are not able to go back to CP8692_M02.
Warning !! Try this own your on risk although it's very safe if you follow the instructions without missing any steps. Don't blame me if you still manage to kill your phone and loose your job :laugh::laugh:
Let's begin !!
Just ensure your device bootloader is unlock before you follow the instructions as it's required to boot 360 Chinese OS on the Indian QiKU.
Download the latest firmware and flash the same with YGDP or Qiku Download Assistant tool. When finished, the device won't boot and still be in fastboot mode. Now boot TWRP recovery from your pc, go to the folder where you have the TWRP recovery and press shift and right click and select "open command window here" and type the following
fastboot -i 0x1ebf boot (recovery name).img
This should boot TWRP on your device.
You can also flash TWRP recovery if wish to,
fastboot -i 0x1ebf flash recovery (recovery name).img
Now boot TWRP
fastboot -i 0x1ebf boot (recovery name).img
When in recovery mode you can use cmd to extract params partition which contain your device model name. Open cmd on your pc and type the following command
dd if=/dev/block/mmcblk0p30 of=/sdcard/params.bak
Once done, you'll have a file name params.bak on your phone's internal memory, copy the same to your pc. Download NotePad++ and install it, link - https://notepad-plus-plus.org/
Only use NotePad++ to edit the params, don't use NotePad. Plus make a copy of your params.bak file and keep it somewhere safe in case you mess up with original params file.
Right click on params.bak and open it with NotePad++, now search CP8692. The device model name would be CP8692_I02 just change I to M and save the changes, now it should be CP8692_M02.
The system partition size is not enough to flash Gapps hence you need to use TWRP recovery resize option.
In TWRP recovery and select > Wipe > Advance Wipe > System > click FS Option > click Resize FS now you shall have more free space in system partition
In TWRP now click reboot then click bootloader, in bootloader press volume up for fastboot mode. On pc open cmd in the folder where you have params.bak saved and type the following command:-
fastboot -i 0x1ebf erase params
fastboot -i 0x1ebf flash params params.bak
fastboot -i 0x1ebf reboot
If everything went well your device should boot Chinese 360 OS, Android 6.0.1 normally.
Now flash modified Gapps in TWRP which you have downloaded. The modified Gapps has Gmail & Hangout beside core apps and rest you can download from play store later.
If you flash bigger Gapps, the device will not boot or it shall be in bootloops coz of Gapps size and if you don't flash Gmail and Hangouts with the modified Gapps and download the same from Play store then it would give you connection trouble.
In case you wish to root then flash SuperSU.zip in TWRP.
Back to the booted device:-
To Activate VoLTE, download QuickShortcutMaker app from play store. Open the app and locate MBN test > click on the dropdown menu > click Try > Tick Volte_OpenMkt-Commercial-CMCC > and last click Activate.
Close the app and go to phone setting > Call settings > and enble VoLTE and you're done. You should see HD sign in the status bar of your phone. Now you can enjoy VoLTE calls.
Download the latest 360OS 2.0 V18 stable version: http://pan.baidu.com/s/1slCmsKP password: i65r
Follow the tutorial to download from Baidu without log-in and download client - https://www.youtube.com/watch?v=cigJh9jg4-c
Download modified Gapps and supersu.zip - https://drive.google.com/drive/folde...ElFemQwTTFXcTQ
Credits:
Goes to me @Zauq for figuring out unlocking bootloader, rooting, modifying TWRP for cp8692_I02 etc. Without the unlocked bootloader the above was not possible.
Goes to @cuongvietnam for instructions to modify params and flashing the same and also about the Gapps size issue
Have Fun :good::good::good:

plz share firmware/rom
good effort bro......kindly wants to tell that new kingroot app is now able to root qiku q terra.....and using app2sd i am able to move max of my apps to sd card ....but i also like ur effort to install android 6 rom in indian qiku.....but i hav a request to plz make a video about whole thing(as that would me more reliable to understand).....and plz share ur downloaded firmware/rom......i hav downloaded android6.cpb file shared by zuaq....so any trick to install directly this rom ?
thx in advance
---------- Post added at 05:28 AM ---------- Previous post was at 04:59 AM ----------
and also i think we can use buildprop edit apk to change build name of indiian qiku (I->M) .....anyway i hav very little knowlg of all this...but try to impliment ur process

Rahulraj2012 said:
good effort bro......kindly wants to tell that new kingroot app is now able to root qiku q terra.....and using app2sd i am able to move max of my apps to sd card ....but i also like ur effort to install android 6 rom in indian qiku.....but i hav a request to plz make a video about whole thing(as that would me more reliable to understand).....and plz share ur downloaded firmware/rom......i hav downloaded android6.cpb file shared by zuaq....so any trick to install directly this rom ?
thx in advance
---------- Post added at 05:28 AM ---------- Previous post was at 04:59 AM ----------
and also i think we can use buildprop edit apk to change build name of indiian qiku (I->M) .....anyway i hav very little knowlg of all this...but try to impliment ur process
Click to expand...
Click to collapse
Help me
I was plash rom but now my phone is hardbrick
My computer is see bootloader but flash file cpd no working

mr_thao said:
Help me
I was plash rom but now my phone is hardbrick
My computer is see bootloader but flash file cpd no working
Click to expand...
Click to collapse
You can load bootloader in your manager device? If you can, so it not brick!

Zauq said:
Hello Friends
A little background first !!
QiKU Q Terra (CP8692_I02) which was sold in India and came pre-installed with 360 OS v21, Android 5.1. The OEM went back to China hence there haven not been any software update for our device. I had been trying to boot latest Chinese 360 OS on Indian Qiku Terra to get updates but after flashing the Chinese version the device would not boot at all and would get stuck in fastboot mode. To revive the device, I had to flash back the V21, I had tried several times but no success.
I even got in touch with the 360 OS engineers over mail with the help of an administrator of Qiku Chinese forum but the engineers said it's not possible to flash Chinese 360 OS on Indian Qiku Q Terra.
I had also been trying to root QiKU and I was able to figure it out all recently.
Check out my post -- https://forum.xda-developers.com/an...i02-unlock-t3493636/post69455878#post69455878
This tutorial is also useful for users of CP8692_M02 who had flashed the v21 on their devices and now are not able to go back to CP8692_M02.
Warning !! Try this own your on risk although it's very safe if you follow the instructions without missing any steps. Don't blame me if you still manage to kill your phone and loose your job :laugh::laugh:
Let's begin !!
Just ensure your device bootloader is unlock before you follow the instructions as it's required to boot 360 Chinese OS on the Indian QiKU.
Download the latest firmware and flash the same with YGDP or Qiku Download Assistant tool. When finished, the device won't boot and still be in fastboot mode. Now boot TWRP recovery from your pc, go to the folder where you have the TWRP recovery and press shift and right click and select "open command window here" and type the following
fastboot -i 0x1ebf boot (recovery name).img
This should boot TWRP on your device.
You can also flash TWRP recovery if wish to,
fastboot -i 0x1ebf flash recovery (recovery name).img
Now boot TWRP
fastboot -i 0x1ebf boot (recovery name).img
When in recovery mode you can use cmd to extract params partition which contain your device model name. Open cmd on your pc and type the following command
dd if=/dev/block/mmcblk0p30 of=/sdcard/params.bak
Once done, you'll have a file name params.bak on your phone's internal memory, copy the same to your pc. Download NotePad++ and install it, link - https://notepad-plus-plus.org/
Only use NotePad++ to edit the params, don't use NotePad. Plus make a copy of your params.bak file and keep it somewhere safe in case you mess up with original params file.
Right click on params.bak and open it with NotePad++, now search CP8692. The device model name would be CP8692_I02 just change I to M and save the changes, now it should be CP8692_M02.
The system partition size is not enough to flash Gapps hence you need to use TWRP recovery resize option.
In TWRP recovery and select > Wipe > Advance Wipe > System > click FS Option > click Resize FS now you shall have more free space in system partition
In TWRP now click reboot then click bootloader, in bootloader press volume up for fastboot mode. On pc open cmd in the folder where you have params.bak saved and type the following command:-
fastboot -i 0x1ebf erase params
fastboot -i 0x1ebf flash params params.bak
fastboot -i 0x1ebf reboot
If everything went well your device should boot Chinese 360 OS, Android 6.0.1 normally.
Now flash modified Gapps in TWRP which you have downloaded. The modified Gapps has Gmail & Hangout beside core apps and rest you can download from play store later.
If you flash bigger Gapps, the device will not boot or it shall be in bootloops coz of Gapps size and if you don't flash Gmail and Hangouts with the modified Gapps and download the same from Play store then it would give you connection trouble.
In case you wish to root then flash SuperSU.zip in TWRP.
Back to the booted device:-
To Activate VoLTE, download QuickShortcutMaker app from play store. Open the app and locate MBN test > click on the dropdown menu > click Try > Tick Volte_OpenMkt-Commercial-CMCC > and last click Activate.
Close the app and go to phone setting > Call settings > and enble VoLTE and you're done. You should see HD sign in the status bar of your phone. Now you can enjoy VoLTE calls.
The latest firmware is 360OS 2.0 (12.28) which is beta and gets weekly update. Download the firmware - http://bbs.360.cn/thread-14613403-1-1.html
Follow the tutorial to download from Baidu without log-in and download client - https://www.youtube.com/watch?v=cigJh9jg4-c
Download modified Gapps and supersu.zip - https://drive.google.com/drive/folde...ElFemQwTTFXcTQ
Credits:
Goes to me @Zauq for figuring out unlocking bootloader, rooting, modifying TWRP for cp8692_I02 etc. Without the unlocked bootloader the above was not possible.
Goes to @cuongvietnam for instructions to modify params and flashing the same and also about the Gapps size issue
Have Fun :good::good::good:
Click to expand...
Click to collapse
I wasn't take dd if=/dev/block/mmcblk0p30 of=/sd card/params.bak
C:\adb>dd if=/dev/block/mmcblk0p30 of=/internalsdcard/params.bak
'dd' is not recognized as an internal or external command,
operable program or batch file.
Hlep me

mr_thao said:
I wasn't take dd if=/dev/block/mmcblk0p30 of=/sd card/params.bak
C:\adb>dd if=/dev/block/mmcblk0p30 of=/internalsdcard/params.bak
'dd' is not recognized as an internal or external command,
operable program or batch file.
Hlep me
Click to expand...
Click to collapse
Have you tried the code in custom recovery mode??? If you're using the code when the device is NOT in recovery mode then you have to use the following code:-
adb shell
su
dd if=/dev/block/mmcblk0p30 of=/internalsdcard/params.bak
Just bear in mind that you have to be rooted to use the above mentioned code and in recovery mode you don't need to be rooted.

mr_thao said:
Help me
I was plash rom but now my phone is hardbrick
My computer is see bootloader but flash file cpd no working
Click to expand...
Click to collapse
What was your device model no when you flashed the rom and which rom version did you flash which caused the brick???

Rahulraj2012 said:
good effort bro......kindly wants to tell that new kingroot app is now able to root qiku q terra.....and using app2sd i am able to move max of my apps to sd card ....but i also like ur effort to install android 6 rom in indian qiku.....but i hav a request to plz make a video about whole thing(as that would me more reliable to understand).....and plz share ur downloaded firmware/rom......i hav downloaded android6.cpb file shared by zuaq....so any trick to install directly this rom ?
thx in advance
---------- Post added at 05:28 AM ---------- Previous post was at 04:59 AM ----------
and also i think we can use buildprop edit apk to change build name of indiian qiku (I->M) .....anyway i hav very little knowlg of all this...but try to impliment ur process
Click to expand...
Click to collapse
Flashing the supersu.zip to root Qiku is the easiest way if you ask me. I tried my best to give the instructions in a simplest way possible making video is not on my mind.
Changing the model no in build.prop would not help in booting Android 6.0.1 on Indian Qiku v21. Had this been so easy I would've done the same a long time ago

update file params.bak edited
step 1 : flash rom china and flash TWRP
Step2: flash params.bak
Step 3: reboot
Done
Link : https://tinhte.vn/threads/danh-gia-chi-tiet-qiku-terra-sieu-pham-den-tu-india.2543152/#post-49187102
Rom restore , rooted and playstore,super lite : https://drive.google.com/file/d/0B1JX0MSsEt63Zzd2MzVMb20wNTA/view

Hello bro,i want to downgrade to 5.1 v021 from 6.0 v18 china rom,but i haven't link rom.zip (i have twrp),give me link rom 5.1v021 .zip,please
Thanks for watching!?

volte is not activating even though option came by quickshortcut..app
android 6.0 successfully installed but...volte is not activating even though option came by quickshortcut..app........also need help to change chinese 360safe apk to change language in english
....thx in advance

Rahulraj2012 said:
android 6.0 successfully installed but...volte is not activating even though option came by quickshortcut..app........also need help to change chinese 360safe apk to change language in english
....thx in advance
Click to expand...
Click to collapse
Help me @Zauq. I am not able to download 6.0 update file from baidu as connection to file gets disconnected after 1 GB of data everytime. I have wasted atleast 10 GB of data due to this. Please help me out if you can upload the file to google.
Thank you in advance.

Rahulraj2012 said:
android 6.0 successfully installed but...volte is not activating even though option came by quickshortcut..app........also need help to change chinese 360safe apk to change language in english
....thx in advance
Click to expand...
Click to collapse
Did you also enable VoLTE in system settings?? I would not be able to change Chinese language in 360safe.apk.

imlb said:
Help me @Zauq. I am not able to download 6.0 update file from baidu as connection to file gets disconnected after 1 GB of data everytime. I have wasted atleast 10 GB of data due to this. Please help me out if you can upload the file to google.
Thank you in advance.
Click to expand...
Click to collapse
My google drive is already full hence won't be able to upload it. Trying signing up Baidu and download the file with Baidu client.

Zauq said:
My google drive is already full hence won't be able to upload it. Trying signing up Baidu and download the file with Baidu client.
Click to expand...
Click to collapse
Thanks for your quick reply. I am not able to sign up on baidu. If you have latest file than please upload on any big file sharing site such as pcloud. That will be very helpful. I am bit of noob on development side of Android. I have developed kernel driver for real time linux but android I am learning. Please share if any good tutorials to start developing for Android. Thanks again @Zauq

imlb said:
Thanks for your quick reply. I am not able to sign up on baidu. If you have latest file than please upload on any big file sharing site such as pcloud. That will be very helpful. I am bit of noob on development side of Android. I have developed kernel driver for real time linux but android I am learning. Please share if any good tutorials to start developing for Android. Thanks again @Zauq
Click to expand...
Click to collapse
There you go --- https://drive.google.com/file/d/0Bwy9M10qfmJLVm9MQTU0N1U2Tnc/view?usp=sharing

Have somebody schematic diagram of qiku phones? Please let me know, if find something.

Hello dear all, I have 2 issues
1) not able to get volte , even though hd voice enabled via quick shortcut app
2)updated to android 6 but even though can't make my sd card as internal storage(option is for only as portable storage present....Just like galaxy s7 I also tried abd command, becoz in s7 also even after android 6 update sdcard as internal is not by default present .....But failed)
Plz help .....Thx in advance bro zuak

Rahulraj2012 said:
Hello dear all, I have 2 issues
1) not able to get volte , even though hd voice enabled via quick shortcut app
2)updated to android 6 but even though can't make my sd card as internal storage(option is for only as portable storage present....Just like galaxy s7 I also tried abd command, becoz in s7 also even after android 6 update sdcard as internal is not by default present .....But failed)
Plz help .....Thx in advance bro zuak
Click to expand...
Click to collapse
1) Do you see HD sign in the status bar after enabling VoLTE through QuickShortcurMaker App??
2) Did you follow similar adb shell command for internal storage?? --- https://www.youtube.com/watch?v=PZLV5STiAW8

1) I m able to get on/off volte settings after quick shortcut apk,but as u ask......No hd sign in status bar
2) yes I had applied same adb shell commands but nothing happens, 360 os restarted but no increment in internal memory I need to format my memory card to use it once again
I request to make a small video for this isse resolution and plz upload if possible

Swipe Elite max : Unlock Bootloader,Unofficial TWRP, Rooting and Stock reflash.

IMPORTANT UPDATE : I have observed that when mounting system R/w device restarts. It means that even after rooting successfully, system is blocking the app. So rooting will not be complete as of now,till further corrections. Rest of the operations are normal, quick reboot apps work properly. and device works normally. So please bear with me.
Freinds , this thread is basically for what the title suggests. After a long time I was able to do it.
I'll update as required, so be patient. and keep watching.
1. Unlock Bootloader
a. Boot device in bootloader from adb in cmd terminal. (To go in fastboot mode, press power and volume down button ).
Please enter these commands, one at a time.
Code:
adb devices
(this will show your device)
adb reboot-bootloader
( device will reboot to bootloader). Then enter this...
fastboot devices
(this will show your device)
fastboot oem unlock-go
( If it shows already unlocked, go to twrp flash. If it is not, It will ask for erasing data, so backup all your data. This will unlock your bootloader.)
2. Flash TWRP
In fastboot mode: continue.......
Code:
fastboot flash recovery twrp.img
(Flash the image I have provided)
You can also try
fastboot boot twrp.img
( to try this image file, if you are scared of bricking the phone.)
3. Flash patched boot.
Code:
fastboot flash boot boot.img
(Flash the image I have provided. This is necessary as otherwise the su zip may not work )
4. Rooting
Please copy the SuperSu zip file to your micro sd card. Now boot to Twrp recovery. My advice is to backup of your system and boot. Then wipe data, dalvik-cache,cache, Internal storage. (Sometimes, format option is required.)
Now flash this zip.
If there are errors anywhere, please tell me and I shall try to correct them.
Updates :
1. Twrp stable added on 8/6/2018
2. Twrp_3.1.0.1 added on 11/6/2018, Removed Old Twrp link.
3. Twrp_3.1.0.1 Link updated on 13.6.2018.
4. Twrp_3.1.0.1 Link updated on 9.7.2019. Removed Old Twrp 3.1.0.1 link.
Downloads
1. Twrp_Stable_3.0.2.0.img: Link
2. TWRP_3.1.0.1_unofficial_SwipeEliteMax : https://drive.google.com/open?id=1n-DfHwC4_WRn_Jlr5FosOb6lW827M5ho
Remember first thing before rooting, do a backup of system and boot.img. Rest is your choice.
2. SuperSu zip: http://www.supersu.com/download Or you can download from anywhere on the net.
3. Patched Boot : Link

Stock Reflash and subsequent Update:
1. Stock Version V12 Reflash :
Remember , boot takes 5-10 mins to come on. So don't panic when device doesn't boot.
If the need arises due to any reason device hangs in logo, first restore only boot which you backed up. If still no change, restore system also.
But if you want to flash stock version , then read ahead.
The FOTA zip did not work for me from adb sideload. So I will recommend the QFIL download.
1. Download Stock Rom and Qualcomm downloader from here
Extract the zip. Install the drivers.
2. QFIL install : Download and install Qualcomm downloader.
It should look like the image in attachments
1. If it shows Flat Build / Meta Build, choose Flat Build.
2. Click "browse" and select "prog_emmc_firehose_8937_lite.mbn" , in the Extracted Stock rom folder
3. Click Load XML and select "rawprogram_unsparse.xml" in the Extracted Stock rom folder.
4. Click Load Patch and select "patch0.xml" in the Extracted Stock rom folder.
5. Click Download. If device is in adb mode, no problem, it will go in download mode automatically.
If it is not, just connect and shutdown device . While it is shutting down, it will connect automatically andf flash will begin.
Do not disconnect while process is on. Be patient.
2. Update to V15 :
After Stock reflash, the update to V15 comes immediately after connecting to internet.
Just incase someone wants to flash it offline , here is the process and file.
1. Recovery Method : Place gobi zip in adb folder . Go to stock recovery. Press Volume up and Power button. Once in recovery, choose "update from adb" .
Enter the following command in cmd console :
Code:
adb sideload update-gobi.zip.
Downloads : Update zip for Version Update from V12 to V15. Link

Yogesh1969 said:
Freinds , this thread is basically for what the title suggests. After a long time I was able to do it.
I'll update as required, so be patient. and keep watching.
1. Unlock Bootloader
a. Boot device in bootloader from adb in cmd terminal, Please enter these commands, one at a time.
2. Flash TWRP
In fastboot mode: continue.......
You can also try
3. Flash patched boot.
4. Rooting
Please copy the SuperSu zip file to your micro sd card.
My advice is to backup your data, then wipe data, dalvik-cache,cache, Internal storage. Sometimes, format option is required.
Now boot to Twrp recovery and flash this zip.
If there are errors anywhere, please tell me and I shall try to correct them.
Downloads
1. TWRP : https://drive.google.com/open?id=0BztfiMqkQrCaQVA4T01pRmlmYXc
Remember first thing before rooting, do a backup of system and boot. Rest is your schoice.
2. SuperSu zip: http://www.supersu.com/download
3. Boot : https://drive.google.com/open?id=19StfSorHM8T89uX07epstCWIUnMsITjz
Click to expand...
Click to collapse
Thanks for help bro. But the tarp zip file u shared needs a password to be opened.

Sorry
partha_h said:
Thanks for help bro. But the tarp zip file u shared needs a password to be opened.
Click to expand...
Click to collapse
Sorry Parth. I linked a wrong image . I now have updated the link. please check and tell me. Dont' hurry in any process. Take care.

Yogesh1969 said:
Sorry Parth. I linked a wrong image . I now have updated the link. please check and tell me. Dont' hurry in any process. Take care.
Click to expand...
Click to collapse
Thanks
Rooted my device successfully. Solved the twrp data decrypt password issue. Mounted super su via usb and my device is successfully rooted.
Thanks again
Now it's time to search for custom roms. Suggest me any ROM u recommend

partha_h said:
Thanks
Rooted my device successfully. Solved the twrp data decrypt password issue. Mounted super su via usb and my device is successfully rooted.
Thanks again
Now it's time to search for custom roms. Suggest me any ROM u recommend
Click to expand...
Click to collapse
Glad to hear that. I don't have any information about specific roms for swipe but we may have to port any aosp or lineage roms for our chipset (msm8937). Once I'm free, I'll get to search that. ....

partha_h said:
Thanks
Now it's time to search for custom roms. Suggest me any ROM u recommend
Click to expand...
Click to collapse
I have ported an AOSP for Redmi 3s. But it has flaws,(wifi, etc.) will take time. Also, I have removed all unwanted apps from the stock. So it is now smaller.

Sorry repeated msg

Yogesh1969 said:
I have ported an AOSP for Redmi 3s. But it has flaws,(wifi, etc.) will take time. Also, I have removed all unwanted apps from the stock. So it is now smaller.
Click to expand...
Click to collapse
Pls share if there is any . Thanks

partha_h said:
Pls share if there is any . Thanks
Click to expand...
Click to collapse
Actually, AOSP and lineage Os ,both are ported successfully. But there are some flaws. Time is a major factor.
Also, I think Our Rom is better than these roms. From twrp I removed all useless apps. So memory has increased a bit.
So, i think instead of marshmallow I should try Nougat or Oreo if possible. Of course time is an enemy . Just hope.

Yogesh1969 said:
Actually, AOSP and lineage Os ,both are ported successfully. But there are some flaws. Time is a major factor.
Also, I think Our Rom is better than these roms. From twrp I removed all useless apps. So memory has increased a bit.
So, i think instead of marshmallow I should try Nougat or Oreo if possible. Of course time is an enemy . Just hope.
Click to expand...
Click to collapse
Hi. U r doing great. Android 7 or 8 would be gud option. Keep up the good work. Thanks

Some one plz send build.prop file of swipe elite max
Some one plz send build.prop file of swipe elite max

Your build.prop attached.
Sachin2015 said:
Some one plz send build.prop file of swipe elite max
Click to expand...
Click to collapse
Is something wrong with your phone or just experimenting ?
Anyways, there are two build.prop files in the system folder, so attached both. good luck.

Yogesh1969 said:
Is something wrong with your phone or just experimenting ?
Anyways, there are two build.prop files in the system folder, so attached both. good luck.
Click to expand...
Click to collapse
Thanx Dude.
How to enable VoLTE for airtel user in this phone ?
How to write imei on this phone ?
and can u send a updated baseband file for this ?

Sachin2015 said:
Thanx Dude.
How to enable VoLTE for airtel user in this phone ?
How to write imei on this phone ?
and can u send a updated baseband file for this ?
Click to expand...
Click to collapse
Hi. This is a very late reply . Sorry for that.
To enable volte, you have to go to
Settings>More>Cellular networks.
Here, you have to enable/On Enhanced 4G Lte mode.
But, you have to remember, few things. Our phone has only one 4g and one 2g slot. You can use any slot for 4g. The other will automatically turn to 2g. This happens when you choose data for that sim.
Another problem you will face if you have the other sim of JIO. It works only in 4g. So if you awnt volte /4g on Airtel and other sim is Jio, you will have no network on Jio as it does not work in 2g/3g.
For Imei , just google SN / IMEI writing softwares from the net. But mind you enter the right IMEIs, as you mind land in trouble if non-matching one is written.
What base band file do you want ? The firmware folder ?

Yogesh1969 said:
Hi. This is a very late reply . Sorry for that.
To enable volte, you have to go to
Settings>More>Cellular networks.
Here, you have to enable/On Enhanced 4G Lte mode.
But, you have to remember, few things. Our phone has only one 4g and one 2g slot. You can use any slot for 4g. The other will automatically turn to 2g. This happens when you choose data for that sim.
Another problem you will face if you have the other sim of JIO. It works only in 4g. So if you awnt volte /4g on Airtel and other sim is Jio, you will have no network on Jio as it does not work in 2g/3g.
For Imei , just google SN / IMEI writing softwares from the net. But mind you enter the right IMEIs, as you mind land in trouble if non-matching one is written.
What base band file do you want ? The firmware folder ?
Click to expand...
Click to collapse
not showing any network..need the modem files

Sachin2015 said:
not showing any network..need the modem files
Click to expand...
Click to collapse
Did you get the files ? If you want the firmware folder, im attaching here.

Xiaomi Black Shark Support/MEGATHREAD

Welcome!
This Megathread is to help bring the different threads together for the Xiaomi Black Shark (SKR-A0 or SKR-H0) since the xiaomi-black-shark tag is broken (at least for me it is). This will also serve as a one-stop shop for people who need general black shark support!
Disclaimer: You (the user) assume the risk for any bootloader unlocking, rooting, or any other modifying of your device. These can lead to phone's being bricked or boot-looped. We aren't to blame if the directions aren't followed to the T!
Tips before modding your phone
1. Stay organized! Make a folder for any files you download or data your backup so you don't lose anything important
2. Backup your user data onto your computer. It is guaranteed 100% of the time that your phone's data will be wiped when installing of uninstalling ANY of the modifications listed below. Unless you have been rooting and unlocking bootloaders for years, you don't want to skip this step.
Common ADB and Fastboot Commands
These are some commands you'll need to get to know:
adb devices: this shows what devices are currently connected to your computer
adb pull: this pulls a file from your phone and saves it to a location on your computer. You will need to specify the location of the file and the save location of the file
adb reboot bootloader: this reboots the phone into fastboot mode to use fastboot commands
fastboot devices: this shows what devices are connected to your computer in fastboot mode
fastboot boot filename.img: this boots the phone with using a image file of your choice
fastboot flash disk_partiton filename.img: this will flash an image file over the disk partition you want.
Example:
fastboot system system.img flashes a new system_a.img over the system parition of your phone's storage. This is where the main operating system is held on the phone.​fastboot reboot: reboots the phone
fastboot continue: boots the phone straight from fastboot into the system, not restarting the phone.
Unlock/Relock your Bootloader
WARNING: This WILL wipe your internal data
On Android, the phone must have an unlocked bootloader to enable some of the common modding features. These steps will unlock your bootloader.
Pre-requisites:
1. You will need the SDK Platform Tools downloaded onto your computer. This has the necessary adb and fastboot programs you will need in order to unlock your bootloader.
2. Enable Developer Options on the Phone
-Go to Settings -> About phone and tap the Build Number 7 times to enable Developer Options
3. Enable OEM unlocking
-For CN Version (SKR-A0):
Go to Settings -> Other Settings -> Advanced Settings -> Developer Options and Enable OEM unlocking. It will give you a warning pop up. Click yes to enable OEM unlocking.
-For Global Version (SKR-H0):
Go to Settings -> Developer Options and Enable OEM unlocking. It will give you a warning pop up. Click yes to enable OEM unlocking.
4. Enable USB Debugging. This lets you use ADB (Android Debugging Bridge) to send commands from your computer to the phone.
-For CN Version (SKR-A0):
Go to Settings -> Other Settings -> Advanced Settings -> Developer Options and Enable USB debugging.
-For Global Version (SKR-H0):
Go to Settings -> Developer Options and Enable USB debugging.
5. Boot into fastboot mode.
-Booting from the Phone:
Turn the Phone off
Press and hold the Volume Down Button
Turn the phone on while holding the volume down button
-Booting from the PC:
Connect your phone to your computer.
Go to where you downloaded the SDK platform tools. The folder name should be "platform-tools" and have "adb" and "fastboot" exe files in it.
Open a command prompt/terminal from that folder.
Run the command: adb devices
A pop up should show up on your phone. Click the checkmark next to "Always allow from this computer" and click ok. Your computer is now allowed to send commands to the phone.​
Now run the command: adb reboot bootloader
You should now be in fastboot mode!
To check if you're in fastboot mode:
Go to where you downloaded the SDK platform tools. The folder name should be "platform-tools" and have "adb" and "fastboot" exe files in it.
Open a command prompt/terminal from that folder.
Run the command: fastboot devices
If your device shows up then you're in fastboot mode! You should also see a line of text that says something like:
"Bootloader Locked"
"Bootloader Unlocked"
Unlocking your Bootloader:
1. If your phone says bootloader is locked:
While connected to your PC run the following commands:
-For SKR-A0
fastboot oem unlock
-For SKR-H0
fastboot flashing unlock
If there is a warning click to proceed with the unlock. THIS WILL WIPE YOUR DATA AT THIS TIME.
If your phone says bootloader is unlocked:
Skip this step!
Your Bootloader is now Unlocked!!
Relocking your Bootloader:[/size]
1. Boot into fastboot mode
2. Connect your phone to your computer
3. Run the Bootloader Lock command
3a. For Both Versions
fastboot flashing lock
WARNING: THIS WILL WIPE YOUR DATA.
Your bootloader is now Locked!
Rooting Using TWRP
Unlocked Bootloader Required!
Required files:
The latest Magisk Zip and APK files...it can be found here
A Computer with the latest SDK Platform tools
TWRP image file found at this thread
Do NOT download the installer.
1. Boot into fastboot mode and connect to your computer
2. Run the command: fastboot boot Name_of_twrp_file_.img
Replace Name_of_twrp_file.img with the name of the twrp image file you've downloaded for the blackshark
Tips:
If your screen is upside down, that's ok! Your touches will be in the same spot, the image is the only thing that's upside down.
On first boot, if TWRP is asking for a decryption password, you will need to wipe your data before going forward.
3. Move the Magisk Zip file to your phone's storage
4. On TWRP:
Click install -> Magisk.Zip file -> Swipe to confirm flash
5. After the install is complete: Swipe to reboot the phone
DO NOT INSTALL TWRP APP IF IT ASKS YOU TO
6. After the phone reboots, install the Magisk apk file
7. If you start the magisk app and it says Magisk is not installed, try rebooting your phone.
8. If you start the magisk app, and it asks to download extra resources, click ok.
You're now rooted!
Install GApps
Installing GApps should only be for the CN version!
You can find the directions and required files in this thread here
Factory Images
For the CN version (SKR-A0)
The factory images can be found on Google Drive here
For the Global version (SKR-H0)
[Guide] Restoring Black Shark 1 Global to Stock OTA bug fixed!
Using Project Treble (GSI) System Images!
What is Project Treble and GSI?
The Generic System Image (GSI) was added into Android 8.0 devices to enable OEM partners and developers to help with updating devices. Using an dual system approach (slot a and slot b) android phones can be updated seamlessly (without rebooting) and recover devices from a bad update.
Project Treble is an extension of this feature to enable developers to update their OS easier to new versions of Android! This includes *drum roll* the ROM commmunity!! So if your phone supports project treble and gsi (which the Black Shark does) we already have ROMs available to us!
The Downside to Project Treble Roms
Our Vendor File isn't compatible with Treble ROMs and we can't use other vendor files (as what I have seen so far) so these bugs will exist for now:
The S logo doesn't turn off. Stays Green lit.
You may not be able to increase screen brightness.
Fingerprint may not work on the Treble ROM.
Installing a Project Treble Rom
YOU WILL LOSE YOUR USERDATA. THERE IS NO GETTING AROUND THIS AS OF NOW.
Prerequisites:
Unlocked Bootloader on your phone and adb, fastboot, TWRP image and the most recent Magisk Zip on your computer.
For CN variants (SKR-A0) you may need to use the Global (SKR-H0) vendor and boot images. These steps were tested on using the Global Images
1. Choose your rom over here
2. Download the ARM64 A/B version of your rom of choice. The Black Shark supports Seamless Updates and it's based on the 64bit architecture (as are most modern phones).
3. Factory Reset your phone. You can do this either through the recovery or through the system settings.
4. Boot into bootloader mode on the phone and connect the phone to the PC.
5. Erase the system partition: fastboot erase system
6. Flash the new system OS: fastboot -u flash system system_image_file.img
7. Boot into TWRP from fastboot: fastboot boot twrp_file.img
8. Tap the DO NOT ALLOW SYSTEM MODIFICATIONS
9. Move the Magisk Zip file to your phone.
10. Click Install -> Magisk Zip -> Swipe to Install
11. Reboot the Phone
That's it! Your screen will be upside down during the media locking process (using a Disable Force Encryption file has not worked for me). Once your get to the setup page you may have to set it up with the screen upside down. THIS IS THE SAME AS HOW TWRP IS UPSIDE DOWN BUT THE TAPS ARE IN THE NORMAL SPOTS. If a warning comes up that's normal.
Android 9.0 Pie News!!!
https://forum.xda-developers.com/android/development/news-black-shark-2-features-coming-to-t3924703
How to Get CN Rom's Shark Space and MI Market onto Global ROM:
https://forum.xda-developers.com/an...-cn-shark-space-mi-market-blackshark-t3927854
Credits:
TWRP by @mauronofrio
Offical XDA Magisk Thread
@gilbert32 for factory global images

Placeholder
---------- Post added at 04:28 PM ---------- Previous post was at 04:25 PM ----------
Thank you for this thread.
I have a question to any Black Shark GLOBAL Owner:
If you have the Stock ROM, updated to the latest version, can you please contact me via private messages, or here.
I need your help to fix my phone to get OTA back running.
Meanwhile, i am figuring out a way to run Custom ROMs beside official ROMs.

gilbert32 said:
Thank you for this thread.
I have a question to any Black Shark GLOBAL Owner:
If you have the Stock ROM, updated to the latest version, can you please contact me via private messages, or here.
I need your help to fix my phone to get OTA back running.
Click to expand...
Click to collapse
No problem!
The CN version gets messed up on the OTA if your active boot is on B. It seems the OTA updates only work with active boot A. It also gets messed up obviously if the backup boot is not the same version. I had to make sure both system_a and system_b were on CN before updating system_a with the OTA.
Hope this helps.. obviously I'm a CN user, but you never know! :good:
gilbert32 said:
Meanwhile, i am figuring out a way to run Custom ROMs beside official ROMs.
Click to expand...
Click to collapse
I already have a linux environment in the works...

I've already successfully booted Lineage OS, OnePlus UI and Resurrection Remix, however they are full of bugs, and completely unusable.
I just need the latest OTA on Global version to make sure it is not related to vendor files/boot image.

gilbert32 said:
I've already successfully booted Lineage OS, OnePlus UI and Resurrection Remix, however they are full of bugs, and completely unusable.
I just need the latest OTA on Global version to make sure it is not related to vendor files/boot image.
Click to expand...
Click to collapse
Shoot me a dm... I'm trying to build without success..I'm also using Omni as a base. Two heads are better than one!

JengaMasterG said:
Shoot me a dm... I'm trying to build without success..I'm also using Omni as a base. Two heads are better than one!
Click to expand...
Click to collapse
AFAIK, it's gonna be pretty hard to build without having the kernel sources. Unless they release them soon, building for the device directly is gonna be a long shot.
However, checkout the treble device forums. You can download and flash roms from that section, and they will probably boot, but you'll have problems with auto brightness, random reboots, etc.
I still can't get the auto brightness and device specific stuff to work.

I have been boot the rros in my CN version,and the auto brighness have been fixed,I think the RRos can used comfortablely,and if you hava tencent QQ,you can join my tencent group,and the number of group is 947723325,welcome all people who like playing blackshark1/helo/2,welcome.

a8530516 said:
I have been boot the rros in my CN version,and the auto brighness have been fixed,I think the RRos can used comfortablely,and if you hava tencent QQ,you can join my tencent group,and the number of group is 947723325,welcome all people who like playing blackshark1/helo/2,welcome.
Click to expand...
Click to collapse
can you share how you did it here?

JengaMasterG said:
The Model version is set by the vbmeta.img files. You should be able to find those here under the factory image files section.
If you want any future support, ask for it in in the megathread so we can keep all the support in one thread :good:
Click to expand...
Click to collapse
Hello im from twrp thread
That after im installing cn version it's keep tell me the build version was global not chinese version and cant update because it's keep show me global build mumber
I have flash it on system A
But when i reflash to global ota update can run update on system b
Thanks

khususgw said:
Hello im from twrp thread
That after im installing cn version it's keep tell me the build version was global not chinese version and cant update because it's keep show me global build mumber
I have flash it on system A
But when i reflash to global ota update can run update on system b
Thanks
Click to expand...
Click to collapse
Can you show us a screenshot of your phone with this build number issue? Also, can you list what steps you took to flash the CN version on top of the Global version?
Normally OTA update won't work when switching the OS from Global to CN and vice versa unless you flash both slots to be on the same version.

JengaMasterG said:
Can you show us a screenshot of your phone with this build number issue? Also, can you list what steps you took to flash the CN version on top of the Global version?
Normally OTA update won't work when switching the OS from Global to CN and vice versa unless you flash both slots to be on the same version.
Click to expand...
Click to collapse
first im format userdata
then flash using twrp for slot a and b
boot > system > vendor
and disableencrypt
after that wipe/davilk
change to slot a
flash using twrp
boot > system > vendor> and flash disableforceencrypt
start system without install twrp
when im boot using slot A
it's shown internal error
i have send the attachment file hope you can help me, thanks

khususgw said:
first im format userdata
then flash using twrp for slot a and b
boot > system > vendor
and disableencrypt
after that wipe/davilk
change to slot a
flash using twrp
boot > system > vendor> and flash disableforceencrypt
start system without install twrp
when im boot using slot A
it's shown internal error
i have send the attachment file hope you can help me, thanks
Click to expand...
Click to collapse
Hmm ok. I haven't seen this issue before, but I also didn't upload the vbmeta.img file for the CN version. The vbmeta handles the model number and could be affecting the build number for your device as well. I have uploaded them to the CN stock files for you to try.

Reply:
Xiaomi Black Shark support are the thing which people need to know now a days world is evolving and things are changing rapidly.

JengaMasterG said:
Hmm ok. I haven't seen this issue before, but I also didn't upload the vbmeta.img file for the CN version. The vbmeta handles the model number and could be affecting the build number for your device as well. I have uploaded them to the CN stock files for you to try.
Click to expand...
Click to collapse
thanks for your help
after uinstall magisk using twrp, my phone can encrypt but only slot b
if i boot using slot a, the error still shown up so i cant encrypt my phone to get OTA update
so if i boot using slot b know the version shown CN version
but if i change to slot a it's show CN but after i choose update the os change to global version
if i update my blackshark localy using *#*#1027#*#* the package dosnt exist
but using this version i can access the light menu and change the color mode
-------
from slot B i cant install the OTA
i still find out how to install the OTA from slot A
i will give the update
thanks

khususgw said:
thanks for your help
after uinstall magisk using twrp, my phone can encrypt but only slot b
if i boot using slot a, the error still shown up so i cant encrypt my phone to get OTA update
so if i boot using slot b know the version shown CN version
but if i change to slot a it's show CN but after i choose update the os change to global version
if i update my blackshark localy using *#*#1027#*#* the package dosnt exist
but using this version i can access the light menu and change the color mode
-------
from slot B i cant install the OTA
i still find out how to install the OTA from slot A
i will give the update
thanks
Click to expand...
Click to collapse
Okay, if anything, I would start from scratch and by flashing the images only. Don't flash the decryption zip until the phone's fully OTA updated.

JengaMasterG said:
Okay, if anything, I would start from scratch and by flashing the images only. Don't flash the decryption zip until the phone's fully OTA updated.
Click to expand...
Click to collapse
okay i will try it, now i just backup boot system vendor vbmeta from slot b and replace it to slot a

khususgw said:
okay i will try it, now i just backup boot system vendor vbmeta from slot b and replace it to slot a
Click to expand...
Click to collapse
Yeah you can do it that way!

JengaMasterG said:
Yeah you can do it that way!
Click to expand...
Click to collapse
hello thanks for helping me, now i have done boot using slot A or Slot B with encrypted device,
after that i install the magisk to make sure magisk not installed in my system
then i check setting update via OTA it's always loop to download the OTA (same if i boot using slot A or Slot B)
then i download the OTA update via PC and extract to sd card and push *#*#1207#*#* for update manually but the package not listed.

khususgw said:
hello thanks for helping me, now i have done boot using slot A or Slot B with encrypted device,
after that i install the magisk to make sure magisk not installed in my system
then i check setting update via OTA it's always loop to download the OTA (same if i boot using slot A or Slot B)
then i download the OTA update via PC and extract to sd card and push *#*#1207#*#* for update manually but the package not listed.
Click to expand...
Click to collapse
Ok. You will need to start from scratch. So format your data, flash the a images over BOTH the a and b systems, boots, vendors, and vbmetas. Next, reboot and DO NOT INSTALL MAGISK. Magisk modifies the system and vendor packages so the OTA won't work. This should be ok, but lmk if you run into issues.

JengaMasterG said:
Ok. You will need to start from scratch. So format your data, flash the a images over BOTH the a and b systems, boots, vendors, and vbmetas. Next, reboot and DO NOT INSTALL MAGISK. Magisk modifies the system and vendor packages so the OTA won't work. This should be ok, but lmk if you run into issues.
Click to expand...
Click to collapse
after i try flash from scratch
and using old vendor b
still i cant do the OTA update

[ROM] [RECOVERY] TWRP RECOVERY AND PORTED LOS16 FOR ALCATEL IDEALXTRA 5059r

UPDATE:
As i don't have much time, here is the link to our Alcatel tetra and ideal xtra development and support group on telegram.
ALL THE FILES THAT USED TO BE LINKED HERE ARE AVAILABLE AT THE MENTIONED TELEGRAM GROUP
https://t.me/Android_General_Chat
Any questions for myself need go there.
Thanks.
LgPWNd
Ok so I am here today to give you a TWRP recovery and A Liniage OS 16 Rom ported from a GSI.
And a quick how to on setting it all up..
DISCLAIMER:
I Am In No WAY responsible for ANYTHING YOU choose to do to your phone.
If you use this and your Dog eats your Cat, Your phone catches fire and burns down your house, or you loose all your game-saves pictures and other files it's NOT MY FAULT.
THIS WILL WIPE YOUR DATA AND FORMAT YOUR PHONE!!!
YOU'VE BEEN WARNED
MY FASTBOOT DOESN"T WORK !
See-This:
Just grab this package I made for @Sloogle_Flugelmann
https://drive.google.com/open?id=1CiGKCPGBJAPvl8R3_24kvdvrQB5V3abI
So requirements are :
#1: Willingness to format your phone and loose all apps and data.{MAKE A BACK-UP}
#2: ADB and Fastboot working on your PC.
#3: The Files I Will Link to or attach .
# Some Time to work on it, and half a Brain
There will be Two methods to accomplish basically the same thing,
Method 1 gives you the long way and it leaves you with the bare basic LOS 16 installed no root no gapps...
on the other hand Method 2 will leave you with LOS 16 and My favorite version of the pixil launcher and stock Gapps included and basically everything working.
METHOD 1-THE LONG ROAD:
STEP 1:
download the package that I will upload for everyone...
STEP 2:
Unlock your bootloader.... there may be multiple ways to do so but for me I enabled usb debugging and OEM unlocking in developers options {if you don't know how to do that you should run far away now !} then I gave the command
Code:
adb reboot bootloader
and this takes you to fastboot mode...
once there issue the following command to unlock your bootloader AND factory-reset the phone
Code:
fastboot oem unlock
then
Code:
fastboot reboot
Now your bootloader is unlocked and your device has been wiped in the process...
so let it boot up then go through the setup wizard and I just skip through everything as we will be wiping it once again in a minute... and just need to get to developer options and re-enable adb...
so do that...
STEP 3: Now that your bootloader is unlocked comes the fun stuff...
Firstly you need an SD-card with at least 4-6 GB free space and before continuing we want to move our LOS-16 System.img to our sd-card so we can install it from TWRP so once that's on the root of Sd-card's storage continue with this guide....
we need to disable DM-Varity to use twrp so we flash a magisk-patched-boot.img
so move the files Patched_boot.img AND twrp_alcatel_5059r_v3-2-3.img to a folder on desktop and open a command prompt /terminal/powershell-window at the file's location.. then issue this command to the phone .
Code:
adb reboot bootloader
and once again we are in fastboot mode.
now we want to use fastboot to replace the stock boot image and stock recovery with our patched boot image and twrp recovery image..
Code:
fastboot flash boot patched_boot.img
then
Code:
fastboot flash recovery twrp_alcatel_5059r_v3-2-3.img
after this we want to reboot to recovery using the hardware keys. because if we don't the stock system will erase our twrp and replace it with stock recovery on boot.
so we do
Code:
fastboot reboot
and soon as you press enter on your keyboard grab the phone and continually hold down the volume-up key and hold the power key .
once you see the alcatel logo and message about unlocked bootloader, you quickly release ONLY the power key for a second then repress and hold it for a count of 5 seconds. then release the power key again and quickly repress it for another 5 seconds and keep doing that for a moment until the screen flashes white then displays the TWRP splash screen.
once we are in twrp it'll ask for the encryption password...
WE DONT HAVE ONE , So just hit Cancel
then it'll ask about system modifications and whatnot,
just swipe to allow modifications.
now we want to head to Wipe > Advanced-Wipe > Format Data
you'll have to type in
Code:
yes
and let it do it's thing.
once done with that we need to reboot to recovery so click the back arrow several times until you are back at twrp's min screen.
head over to Reboot>Recovery
the phone should reboot right back to twrp, you shouldn't see the encryption password screen this time as we formatted DATA.
so now swipe to allow modifications and head back to
Wipe>Advanced-Wipe and check the boxes for system,dalvik-cache,cache,data....
then swipe to wipe them.
then you want to hit the back arrow again till at the main twrp screen again.
Head to Install click on select storage, choose your Sd-card
Click on install zip to change it to install image.
select the LOS image we moved to the Sd-card prieviously,
click on System as the install location.
and finally swipe to flash it.
let it do it's thing.
once completed you will want to click the back arrow again until main twrp screen and reboot to recovery once more....
now once in recovery again you swipe to allow modifications and need to replace the GSI's build.prop file with the one I am including in the zip.
I used adb to accomplish this...
on your PC move the included build.prop file to your working directory{folder your working out of}
and use the terminal/command prompt/powershell to give the following commands
Code:
adb devices
you should see the device identified by serial number and the word recovery next to it
then
Code:
adb shell
you should have a root shell on the device,
Code:
rm -rf /system/build.prop
then
Code:
exit
now your back to pc terminal so type:
Code:
adb push build.prop /system/build.prop
Code:
adb shell
back to root shell
Code:
chmod 0644 /system/build.prop
and then
Code:
reboot now
at this point your phone should reboot and everything was done correctly it'll go past the alcatel logo and bootlock message and then display the LOS 16 boot animation then it'll show a funny looking screen that has an android guy and the message " Please wait while your device is being encrypted"
it'll have a progress counter and when the count-down reacheds zero it'll just hang there....
that's ok, hold the power key until the phone reboots and you should get the los bootanimation followed by the LOS setup wizard start screen.
and you go through the set-up wizard and you'll be in LOS 16 PIE
Now if you want google apps to work there's a few more steps and they will be the same for both method 1 and method 2
if you flash gapps after rebooting from that you'll get a million messages about google play services and google apps crashing ... it's ok
you need to enable usb debugging in the LOS 16 and then sideload the apk ( Device+ID.apk )
Code:
adb sideload "Device+ID.apk"
once installed
open it to get the GSF registration number for your device.
then if you open the play store you'll be greeted by the google DEVICE UNCERTIFIED page...
Don't fret , this is why we fixed the build.prop to reflect our devices orig. build fingerprint...
So scroll down to the bottom of that page and see the last option about Custom Roms
there is a link there... long press that link and choose open in browser
you'll be greeted by the registration page for google...
make sure you are signed into google through your browser...( <---VERY IMPORTANT ) by opening another page to google gmail or the like and signing in with your google account.
then go back to the registration page and hit refresh ...
now it should recognize you by your gmail account in the top right corner i think.
anyhow... go to that ( Device+ID.apk ) that we sideloaded and click on the second set of numbers down the list it should mention (GSF) and choose copy . it'll copy the numbers to your clipboard.
now go back to the browser page from google about registration and paste the copied number into the place next to the (Register) button and then click the register button
it should then list your id converted to decimal on the page...
I did this several times from my PC and got no where but after doing it from the phone it's self a couple minutes later i clicked on one of the error messages about google play services and wholy-krap it finnally let me open google-play-store.
at this point your ready to go....
for an informative article with pictures about this check here:
https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/
Now for Method 2
method two involves all the same steps as method 1 up until you get to TWRP... except that instead of moving the LOS16 system.img to your Sdcard before begining you'll want to extract the alcatel-idelXTRA-5059r-LOS16-modded-2019-05-23.zip I've included and move that whole folder to the sdcard...then
go back and read method 1 and once you are booted into twrp for the first time STOP and come back here to Method 2
Now once you get to twrp the first time the first thing to do is click cancel on the encryption screen then swipe to allow modifications on the next screen. then once at the main twrp screen we need to make a back-up that we will likely never use...
so go to Backup>choose storage (micro sd-card) and then make a back-up, Name the back-up My-Backup so that you can easily find it later. to save space and time I'd recommend backing up just the boot partition.
that'll complete quickly...
now for the weird work-around/Dirty-Hack stuff
you should have the contents of alcatel-idelXTRA-5059r-LOS16-modded-2019-05-23.zip a folder called (alcatel-idelXTRA-5059r-LOS16-modded-2019-05-23) on the root of your sd-card's storage...
and we just made our first back-up from twrp of our boot partition.
so from the main twrp screen we go to Advanced>File-manageer>external_sd we should find a folder labeled(TWRP)
inside that should be a folder labled (BACKUPS) and inside that should be yet one more folder with your device's serial or android ID as the label mine is (49NJ6TORP****VRG) your's may read differently. and finally inside That folder you should find the back-up you previously made (My-Backup) if you followed my instructions.
now we need to go back to the root of our sd-card's storage by clicking (up a level) several times and then click on the folder i had you move there earlier (alcatel-idelXTRA-5059r-LOS16-modded-2019-05-23) and once you click it you'll see files inside look down to the right hand corner in twrp
you should see a little blue folder button with a check-mark , Click that button
then it'll show you options....
click (Move) button then click (up a level) it'll look like it took you all the way back to the beginning top level of file manager, now we navigate to where we want the folder Moved to, so click external_sd > TWRP>BACKUPS>49NJ6TORP****VRG"or what-ever it named your device" > and when you see your (My-Backup) folder STOP... now click the folder button bottom right again, and you're presented with a screen saying moving blah blah blah : to : blah blah blah...
just swipe to move it there.
once you've done that click the back arrow to leave file manager and back out to the main twrp screen again...
Now click Restore>select storage> Micro Sdcard >ok and you should see two things to choose from...
(My-Backup) " the one you created earlier "
and
(alcatel-idelXTRA-5059r-LOS16-modded-2019-05-23)
obviously choose the second one (alcatel-idelXTRA-5059r-LOS16-modded-2019-05-23)
it'll ask you which partitons to restore
make sure ALL of the available boxes are checked should be boot, recovery, cache, and system
then swipe to restore...
after that's done we want to make sure we don't have any issues so back out to the main twrp screen
go to Wipe>Advanced Wipe and choose Dalvik/art Cache and also Cache and Data
swipe to wipe.
then back out once more and goto Wipe>Format Data and type yes and click the blue check mark on the keyboard to continue
after formating data
back out to main twrp screen and go to Reboot>System and if prompted choose NOT to install TWRP app
it wont work for you any way.
it should now reboot and do the please wait while encrypting your device thing again ...
after it counts down to zero it'll hang so just hold down the power button until it reboots and you'll get los boot animation followed by Los setup wizard.
go ahead and setup your device once completed the setup wizard you'll want to follow the part at the end of Method 1 above to get google apps and playstore working.....
then you're Done.
enjoy
NOTE with method two you'll also have a modified /system/etc/hosts file so you'll basically have ad malware and porn protection too. if you don't want that you can replace the content of your hosts file with
Code:
127.0.0.1 localhost
::1 localhost
from twrp etc.
if you like what I've done and want to motivate me to do even more please click thanks and consider a small donation of the price of a coffee or stout Beer
AIO-Package = https://drive.google.com/open?id=14fXqm4fjHtNJ8gm9M2SUdybuFAbIyHjJ
EDIT Somehow forgot to add the magisk patched boot.img to the file
will upload separately later
EDIT: 2
here's the zip with patched_boot.img
UNZIP IT
https://drive.google.com/file/d/1R8Sar9yx6mI7by02v83uEprmBOc7_9I1/view?usp=sharing
Edit 3:
Alternate "Better" recovery. !
there are two other recovery ports and I'd recommend either of them over this TWRP.
That being said, if you use method 2 to restore my back-up above...
Please do so with the twrp linked here as thats what made the back-up.
Here's The link to other better recoverys...
keep digging for it
almost there..
.
Link: https://forum.xda-developers.com/android/development/recovery-pitchblack-redwolf-recoverys-t3947609
EDIT 4:
Making Magisk Just WORK Dammit!
So here is something Nice, We now can have Magisk root on any Pie GSI's by flashing this zip-file .
NOTE TO THREAD HOPPERZ:
THIS IS INTENDED ONLY FOR THIS DEVICE.
IT WILL LIKELY WORK ALSO ON THE ALCATEL TETRA SINCE THE FILES AND PATH ARE THE SAME
DO NOT FLASH THIS TO ANYTHING ELSE!!!
Credit for this go's to a guy who figured out the lib file was missing in most gsi images,
My-self for putting it all together in a flashable zip.
and to @TheExploitedOne for his help fixing error 6 on my updater script and blindly flashing it first
The-Good-Stuff: https://drive.google.com/open?id=1qgZJyEOfVuN7POv_YKAunm-62oNRFhUb

Credit where it's due:
 @Sloogle_Flugelmann and @riskybusiness
for the thread located:
https://forum.xda-developers.com/android/help/alcatel-idealxtra-5059r-root-t3885536
Which got me thinking....
also 
 @Andy Yan for building the GSI that I used to port this
 @phhusson for all the work on treble and GSI'S that made this possible
 @topjohnwu for magisk
and Alcatel / TCL for making it easy this time.

Ok so I found a way to disable forced encryption.
allowing TWRP to use our /Data partition again Yeay!!!
So here's how to do it...
Download the attached file from this post....
put it on your desktop or what ever folder your working out of...
Extract IT and find fstab.mt6739
open your terminal/CMD window and then boot to TWRP.
once in TWRP go ahead and go to Mounts>vendor
and make sure /vendor partition is mounted...
then go back to the pc and type...
Code:
adb shell rm -rf /vendor/etc/fstab.mt6739
Code:
adb push fstab.mt6739 /vendor/etc/fstab.mt6739
Code:
adb shell chmod 0644 /vendor/etc/fstab.mt6739
now go back over to fone, and in twrp back out to main screen and then go to wipe>format Data >type yes
let it do that....
once finished go ahead and reboot to android system
It'll boot up and takes a few minutes to go through the whole set-up wizard again.
but this time you will NOT see the darn little Encrypting the Krap out of android screen...
PROFIT !!!!!
Method 2:
NO PC NEEDED
Download attached file , EXTRACT IT , move fstab.mt6739 to your external sd card....
reboot to twrp,
in twrp at main screen go to
Mount>vendor and make sure /vendor is mounted, and mount> Micro SD Card make sure you have sdcard mounted...
then hit back arrow.
from main screen go to Advanced > File Manager > vendor > etc > fstab.mt6739
click the file and then click Delete
now scroll back to top (Up A Level) > (Up A Level) > external_sd
now look for the file you downloaded with the name fstab.mt6739
click on it then click Move
then once again vendor > etc
now click the little blue folder icon bottom right corner
It'll say,
Moving
Blahblahblah
to
Blahblahblah
just swipe to confirm
after that hit Back
now to fix the permissions
(up a level) > vendor > etc > click on fstab.mt6739
click on chmod
it'll show
Permissions
0000
go ahead and delete the zeros and then type 0644
then hit the checkmark to complete action (bottom right corner)
once done just hit back back back...
till main twrp screen
now to format data to remove the encryption...
back out to main screen and then go to wipe>format Data >type yes
let it do that....
once finished go ahead and reboot to android system
It'll boot up and takes a few minutes to go through the whole set-up wizard again.
but this time you will NOT see the darn little Encrypting the Krap out of android screen...
PROFIT !!!!!
If this helped you, please consider the thanks button....
If this saved your day maybe you'd like to buy me a cup of coffee?
ENJOY

Network unlock package available now
Ok so I have found a way to network unlock the fone but developing it has cost me nearly $80
I am considering sharing a restore package that you can use to restore a back-up from twrp to get your fone Unlocked for any GSM carrier...
But as I have seen NO ONE post in this thread yet, I'll save it...
I may even make it a gift for anyone who donates anything more than $3 to me for my time effort and expenses in developing all this stuff.
if anyone's interested either hit thanks and post about your interest here...
or shoot me a private message...

Got it fully rooted
I got the los 16 pie gsi rooted through a long combination of dirty hacks that in the end allows the official los 16 addonsu to work correctly.
Don't know if ill ever get around to sharing exact details but I will upload a rooted los 16 rom here very soon
will work on that getting that rooted system.img uploaded sometime this week hopefully

Alcatel Da And Auth Files
I scoured the net and finally took apart another program to get these but here's the AUTH & DA files for this device....
also going to add an archive containing all ALCATEL DA and AUTH files I have now....
of course it seems I'm the only one interested in this device...
so probably no one will ever think to look here for them...
but if you do , And if this helps in any way....
Don't forget to click thanks button

Come a long way on this device...
Too bad no one else seems interested ?

Fastboot mode is disabled on mine. adb reboot bootloader just restarts mine.

I have a fix for you
Sloogle_Flugelmann said:
Fastboot mode is disabled on mine. adb reboot bootloader just restarts mine.
Click to expand...
Click to collapse
I'll load up a lk.bin that you can flash using root and DD.
I'll include a ReadMe with exact instructions.
For temp root to flash the lk.bin you're gonna want to use mtk-su
I'll include everything needed in a zip and load it up here.
May take me a little bit since I'm hanging with the family for 4th.
Happy 4th of July

Sloogle_Flugelmann said:
Fastboot mode is disabled on mine. adb reboot bootloader just restarts mine.
Click to expand...
Click to collapse
@Sloogle_Flugelmann
Thanks for bringing that to my attention,
I been so busy developing for the tetra lately because no one seemed interested here.
If you go back and re-read OP,
I've added a fastboot fix zip with everything needed and instructions
the zip is for a windows user ,
for linux just replace the ./adb.exe with adb
in the commands issued to pc
Let me know if you need help.

LgPWN'd said:
@Sloogle_Flugelmann
Thanks for bringing that to my attention,
I been so busy developing for the tetra lately because no one seemed interested here.
If you go back and re-read OP,
I've added a fastboot fix zip with everything needed and instructions
the zip is for a windows user ,
for linux just replace the ./adb.exe with adb
in the commands issued to pc
Let me know if you need help.
Click to expand...
Click to collapse
Awesome! Thank you. Yeah I just got this phone as a secondary/backup phone and assumed nobody would even be interested in doing anything with this phone. Was kinda surprised to see any progress.
Also, I recommend using Wordpad because Notepad made it one long line of text

Regardless of what or how many times I try, I always end up on a stuck boot screen with circle crossing the screen on the LOS16 rom.

Sloogle_Flugelmann said:
Regardless of what or how many times I try, I always end up on a stuck boot screen with circle crossing the screen on the LOS16 rom.
Click to expand...
Click to collapse
It take a while to boot up
Did u try the backup/restore method?
It always takes mine a bit to boot up.

LgPWN'd said:
@Sloogle_Flugelmann
Thanks for bringing that to my attention,
I been so busy developing for the tetra lately because no one seemed interested here.
If you go back and re-read OP,
I've added a fastboot fix zip with everything needed and instructions
the zip is for a windows user ,
for linux just replace the ./adb.exe with adb
in the commands issued to pc
Let me know if you need help.
Click to expand...
Click to collapse
Can you patch fastboot in my Alcatel A7 XL?? Please, it's disabled...
I can use mtk-su since is arm64 MT6750.
Here is the lk.bin:
https://drive.google.com/file/d/1-ATD4aw5tQZHSWpvcM70qhdAcOYGCXKM/view?usp=drivesdk

Rortiz2;798[INDENT said:
[/INDENT]49897]Can you patch fastboot in my Alcatel A7 XL?? Please, it's disabled...
I can use mtk-su since is arm64 MT6750.
Here is the lk.bin:
https://drive.google.com/file/d/1-ATD4aw5tQZHSWpvcM70qhdAcOYGCXKM/view?usp=drivesdk
Click to expand...
Click to collapse
The issue will be this:
If I modify that in any way and you flash it
You will have a brick .
You can only flash modded images after you unlock the bootloader.
Best advice is to look for older or other copies of firmware from the manufacturer and hopefully one of those will allow you to get fastboot.
Anything not signed by manufacturer will brick u .

LgPWN'd said:
The issue will be this:
If I modify that in any way and you flash it
You will have a brick .
You can only flash modded images after you unlock the bootloader.
Best advice is to look for older or other copies of firmware from the manufacturer and hopefully one of those will allow you to get fastboot.
Anything not signed by manufacturer will brick u .
Click to expand...
Click to collapse
Ugh, so it will enter in a red state and it will refuse to boot...
So there's no any way?
PS: I can't find stock FW in any site...

LgPWN'd said:
@Sloogle_Flugelmann
Thanks for bringing that to my attention,
I been so busy developing for the tetra lately because no one seemed interested here.
If you go back and re-read OP,
I've added a fastboot fix zip with everything needed and instructions
the zip is for a windows user ,
for linux just replace the ./adb.exe with adb
in the commands issued to pc
Let me know if you need help.
Click to expand...
Click to collapse
LgPWN'd said:
It take a while to boot up
Did u try the backup/restore method?
It always takes mine a bit to boot up.
Click to expand...
Click to collapse
I left it for over 30 mins. I'll try the backup/restore method tonight.
UPDATE: The backup/restore method worked and I was able to get it booted. Thank you so much! This is awesome

What would u like to see for it next?
Sloogle_Flugelmann said:
Awesome! Thank you. Yeah I just got this phone as a secondary/backup phone and assumed nobody would even be interested in doing anything with this phone. Was kinda surprised to see any progress.
Also, I recommend using Wordpad because Notepad made it one long line of text
Click to expand...
Click to collapse
Ive got several other recoveries for it.
Going to start work on several other device specific
System images for it.
Open for suggestions

I've been intrested a while now!
NOTE: I do have fastboot now from your package
Are you able to upload a copy of the unlocked bootloader images? I currently can't use fastboot because it requires USB 2.0 rather than 3.0 (which is bs in my opinion). I just plan to flash the images and unlock without the data wipe. Thank you again for your work sir!!!!

You'll have to use fastboot to unlock bootloader.
TheExploitedOne said:
I've been intrested a while now!
NOTE: I do have fastboot now from your package
Are you able to upload a copy of the unlocked bootloader images? I currently can't use fastboot because it requires USB 2.0 rather than 3.0 (which is bs in my opinion). I just plan to flash the images and unlock without the data wipe. Thank you again for your work sir!!!!
Click to expand...
Click to collapse
No way around fastboot oem unlock....
But.
I've done it from another Android with a usbotg cable between the two

Lenovo S5 Pro - L58041 (Global) [2020.03.21]

Welcome to this little thread in which I'll provide every useful information about this device based on my and other users's experiences. If you know something, that I didn't mention, please reply to this thread in order to help out each other even more effectively. Thanks and pleasant reading!​
The Lenovo S5 Pro is a very decent mid-ranger with good specs and even better pricing. We all know, that chinese manufacturers tend to install bloatware on their products time to time. In our case, Lenovo didn't release a single update since 2018 Novemer to this device. It means, that it came out with Android 8.1 Oreo (2018 November Security Patch) and left untouched. This is even worse, than Meizu which is famous for it's neglecting policy of software updates for global users. Now, that we know all this, it's not a surprise, that we are here on our favourite developer forum.
*** General information | Links | Downloads | Credits ***​
The official global firmware is now saved and available (thanks to our forum member nikosddesign) here: download & link to the post
Everything you will possibly need (PC software, drivers, stock camera app, VoLTE modem etc...) is available in this Yandex Disk, you just have to navigate to each one. (Most of the content is in russian, since Yandex is the russian Google, but it's not hard to find the files you'll need).
The previous links and the following tutorials are only available, because suninterbru (from 4pda forums) and radiationofthenation provided these informations and the tutorials, also so much thanks to everybody on the 4pda forums, who provided useful information and files, большое спасибо!
Even though the bootloader unlock, TWRP install and rooting should not cause data loss, be careful and create a backup. You can back up only your files and data or your whole ROM, it's up to you.
Please note, that after you've unlocked your bootloader, everytime your reboot or turn on your phone a warning will pop up during the boot process for about 1 second. On Android 9.0 Pie vendor the message pops up for about 5 seconds. The warning is about the side effects of modifying the system software and it also says, that it is not recommended to store any personal data on your device anymore. Please ignore this message, since it's only popping up, because manufacturers usually don't like, if you modify your device.
Pro tip: If you keep pressing your power button for a little longer you can skip the alert and boot faster.
*** Bootloader unlock ***
Please note, that your warranty will become invalid/void after you unlock your bootloader or root your device.​
0. In your device's developer settings enable bootloader/OEM unlock and USB debugging.
1. Visit the official ZUI bootloader unlock website.
2. Enter your IMEI1 number in the first field. (You can find your IMEI numbers in Settings\About or in the dialer enter: *#06#).
3. Enter your serial number in the second field. (You can find your serial number in the fastboot menu). The one in the settings is not good in this case! (To access the fastboot menu, turn off your phone, then press the power button and after you see your screen light up, immediately press the volume down (-) button or while it's turned on and USB Debugging is enabled, simply type in the terminal/cmd ,,adb reboot bootloader").
4. In the next field enter your email adress. (Please note, that Tutanota won't work, Gmail is recommended or other not secure email providers).
5. Enter the verification numbers in the last field.
6. Tick the checkbox.
8. Click on the blue button.
7. Now check your inbox and/or spam folder, because Lenovo just sent you your custom sn.img, only for your phone.
8. Save the sn.img to your PC and install ADB drivers system-wide. (Thank you Snoop05 for your work)!
9. Open a terminal/cmd on Windows. You should be in the same directory, where your sn.img file is, with the terminal. To change directories type ,,cd your directory goes here" and hit ENTER.
10. Run the following commands:
- adb reboot bootloader
- fastboot flash unlock sn.img
- fastboot oem unlock-go
11. Congratulations! Your bootloader is now unlocked!
*** TWRP Recovery ***​1. Download the .img file from here.
2. The steps are similar to the bootloader unlocking:
- adb reboot bootloader
- fastboot flash ,,downloaded" .img
- After the flashing is done DON'T reboot to the system, instead navigate to the ,,Reboot Recovery or Recovery Reboot" option and select it. (Volume keys and power key - you know the drill) This will ensure, that the TWRP Recovery doesn't get ereased on reboot(s)!
3. After you've successfully rebooted into TWRP, you should root your device with Magisk, to prevent the recovery erasure!
*** ROOT ***​1. The good old SuperSU is no longer in the picture, but don't worry a new player is in the game. Download Magisk from here. (Thank your for your work topjohnwu)!
2. After you've downloaded the flashable .zip copy it to the main directory/root of your device.
3. Reboot to TWRP.
4. Click install, select the flashable .zip file.
5. The installation process should start.
6. Reboot, after finished.
7. Check if Magisk Manager is installed or not, if yes tap and update it.
8. If you did not succeed, please check the Magisk topic for solutions or reply to this thread.
*** Factory reset | Stock ROM | Unbrick | LOST IMEI/PERSIST/EFS | QCN BACKUP/RESTORE ***
!!! NEVER EVER TICK ,,ERASE ALL BEFORE DOWNLOAD" IN QFIL, OTHERWISE YOU WILL LOSE YOUR IMEI AND THE ABILITY TO CONNECT TO MOBILE NETWORKS !!!​
If you accidentally clicked on that option you will have to restore someone elses QCN backup. (It will not work, if you backup your own QCN and rewrite your IMEI and restore it, so do not waste your time with that)! Luckily, a member of the 4PDA forums published their qcn backup. (большое спасибо geepnozeex)! QCN backup for Lenovo S5 Pro. (I modified the link, because the original one is no longer valid)
1. Download the linked QCN file.
2. Make sure, that you are on one of the Stock ROMs, however the recommended ROM is this one.
3. You will have to be rooted to put your device in diagnostics mode. To do that, follow this tutorial.
4. You will have to edit the QCN file with HxD, in order to write your own IMEI into.
5. Open the file with HxD and search for 08 8A 76 06 06 14 57 95 32. This is the IMEI 2. You will have to insert your IMEI 2 from the box here, but first you will have to convert it into Hexadecimal numbers.
6. Convert your IMEIs into Hexadecimal numbers here.
7. You will have to rewrite and insert your values insted of the previous one.
8. Search for 08 8A 76 06 06 04 67 98 72. This is IMEI 1. Convert your IMEI 1 into Hexadecimal numbers, too and replace.
9. Save the file (Ctrl + s)
10. Open QFIL and click on Tools, then QCN Backup/Restore.
11. Choose the QCN file, you wrote your IMEI into.
12. Click on Restore QCN.
13. There is a chance, that the process/progress bar won't finish till the end. No problem, just reboot to EDL mode through TWRP/Advanced and restore the recommended stock ROM.
14. You should have everything working fine, now.
To factory reset or unbrick your device, follow this tutorial on 4PDA. [Don't panic you don't have to know russian, just follow the instructions on the pictures! To see the pictures, click on the bold text.] ,,(спойлер (+) (Инструкция по прошивке)" ~ or ~ Download any of the previously linked STOCK ROMs to your device's main folder and flash them through TWRP. Most of them are in flashable .zip formats and should work well. A simple factory reset in TWRP is recommended before installing any of the ROMs, be careful this action will erease your data from your phone!
(Please note, that most of the time you'll have to use the QPST/QFIL method, because the flashable .zip files always expect a specific vendor version, usually a lower one, so you can upgrade with flashable .zips, but possibly can't downgrade, so you have to use QFIL)!
*** GSI custom ROMs ***
Our device is arm64-aonly, so please only use according GSIs. Note, that I will link only those GSIs, which are booted successfully on my device!​
~ phhusson's official GSI list: here
~ phhusson's AOSP GSI (Android Open Source Project): here
~ developerluke's ExpressLuke GSIs: here
~ eremitein's CAOS GSI Project: here
~ eremiten's LOSQ GSI Project: here
~ igors1974's Amber GSIs: here
~ tunasahinn's and yek4perf's Tunahan's GSI builds: here
~ mrsshunt3r's albus-gsi: here
Note, that you should keep up with the developments and update your system, if needed! These are just a few GSIs, that I've tested personally on my phone, but you can always keep up with the latest news and try new GSIs out, thanks to phhusson's official GSI list!
*** How to flash an Android 10 GSI ***​
1. Download the latest custom phh-magisk from here. (Thank you developerluke and phhusson)!
2. Download the latest Disable_Dm-Verity_ForceEncrypt from here. (Thank you Zackptg5 and others)!
3. Download your desired GSI.
4. You can flash from an USB-OTG flash drive or from the storage of your phone. (I personally have a dedicated USB for this purpose).
4.1 If you are coming from stock ROM you will most likely need to Format Data in this step, because the Disabler won't be able to decrypt the data and, that will cause a stuck at the boot logo!
4.2 Reboot Recovery
5. In TWRP perform a normal factory reset
6. Flash Disable_Dm-Verity_ForceEncrypt. (Cache wipe is optional).
7. Flash your GSI image.
8. Format Data (Skip this step if you already did this in 4.1)!
9. Reboot Recovery (Skip this step, too if you already did this in 4.2)!
10. Flash Magisk-phh
(11. Wipe cache/dalvik).
12. Reboot System
13. Enjoy!
*** Possible GSI bugs ***
Please note, that bugs can differ/vary on different GSIs, the numbers are not fully accurate!
​
1. The default camera app will work, however it doesn't support HDR, panorama or portrait modes. It also can't record in 4K resolution. Freezing is also possible. ~ 50%
2. First time, when you open the camera it'll stuck on loading, but after you go back and open it again it will work flawlessly. ~ 50%
3. No audio/microphone during phone calls. ~ 15%
*** Guaranteed GSI bugs*** ​1. The infrared face unlocking will not work, only fingerprint authentication is working. ~ 100%
2. You won't be able to charge your device while it's turned off, after you plug it in, it will automatically boot up. ~ 100%
3. Auto brightness. ~ 100% (There is a fix for auto brightness below)!
*** Camera fix (GSI) ***
(If you get ,,serious camera error" or your camera freezes on HDR)​
1. Download a custom camera app, where you can manually adjust the ISO level.
2. With OpenCamera, for example you have to adjust ISO to 800 and never above, because your camera will freeze!
3. So, always keep ISO 800 or under. With these settings even HDR shots are working!
*** Auto brightness (GSI) ***​1. Download framework-res__auto_generated_rro.apk from this thread.
2. Follow the instructions, which are described in this post. (You will need to have root to use ,,su" commands).
3. Thank you MishaalRahman and kAs1m for the apk and the instructions!

Twrp disappears when restarting
Help, twrp disappears when restarting. After installing it by: "fastboot flash recovery trwp.img". right there I start it with the "Vol + Power" keys and it starts correctly but when you turn it off and back in, "stock recovery" appears again. I also installed it again using the same twrp, but it disappears again.

kcire_eae said:
Help, twrp disappears when restarting. After installing it by: "fastboot flash recovery trwp.img". right there I start it with the "Vol + Power" keys and it starts correctly but when you turn it off and back in, "stock recovery" appears again. I also installed it again using the same twrp, but it disappears again.
Click to expand...
Click to collapse
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.

Halwer said:
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Click to expand...
Click to collapse
It didn't work, given: "fastboot: usage: unknown reboot target recovery" Sorry for the long time to answer, I only have mobile data, and from this same mobile I answer, and I use google translator, I'm from Mexico.

Halwer said:
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Click to expand...
Click to collapse
Foto

kcire_eae said:
Foto
Click to expand...
Click to collapse
Well, it looks good. Maybe only " reboot recovery " is enough.

Halwer said:
Well, it looks good. Maybe only " reboot recovery " is enough.
Click to expand...
Click to collapse
It didn't work, friend, but I appreciate the help.

kcire_eae said:
It didn't work, friend, but I appreciate the help.
Click to expand...
Click to collapse
I'm sorry. Do an internet search and check related TWRP forums for solutions for this specific issue. For me everything is working fine. Are you sure you unlocked your bootloader first?

Halwer said:
I'm sorry. Do an internet search and check related TWRP forums for solutions for this specific issue. For me everything is working fine. Are you sure you unlocked your bootloader first?
Click to expand...
Click to collapse
Help, I did the following and I no longer start my mobile:
-fasboot flash recovery twrp.img.
-fasboot flash boot twrp.img.
-fasboot reboot.
now just start twrp even if restart restart twrp again, in the twrp browser my sdcard files are shown, maybe you can still help me please.

kcire_eae said:
Help, I did the following and I no longer start my mobile:
-fasboot flash recovery twrp.img.
-fasboot flash boot twrp.img.
-fasboot reboot.
now just start twrp even if restart restart twrp again, in the twrp browser my sdcard files are shown, maybe you can still help me please.
Click to expand...
Click to collapse
You should not have flash the recovery image to the boot partition. These partitions are not the same, be careful! Now you can save your data from TWRP via MTP connection to your computer. After that restore your phone with QPST to the latest pie ROM or to the oreo ROM from yandex. The oreo ROM is flashable from recovery, it is easier.

Halwer said:
You should not have flash the recovery image to the boot partition. These partitions are not the same, be careful! Now you can save your data from TWRP via MTP connection to your computer. After that restore your phone with QPST to the latest pie ROM or to the oreo ROM from yandex. The oreo ROM is flashable from recovery, it is easier.
Click to expand...
Click to collapse
Is it possible to just flash the boot partition (boot) again, if I get the boot.img from another rom?
I don't want to lose the stock rom:crying:

kcire_eae said:
Is it possible to just flash the boot partition (boot) again, if I get the boot.img from another rom?
I don't want to lose the stock rom:crying:
Click to expand...
Click to collapse
Maybe you can try to download a ROM file, extract it and flash the boot image, but I'm not sure if it is going to work.

Halwer said:
Maybe you can try to download a ROM file, extract it and flash the boot image, but I'm not sure if it is going to work.
Click to expand...
Click to collapse
I'm going to try, and even,
on this page there are android 9, will it be true?
"https: // mirrors.lolinet.com/ firmware / lenovo /l58041/"
but first I will do it with the "O" stock, which you mention here.
I hope it will work again.

kcire_eae said:
I'm going to try, and even,
on this page there are android 9, will it be true?
"https: // mirrors.lolinet.com/ firmware / lenovo /l58041/"
but first I will do it with the "O" stock, which you mention here.
I hope it will work again.
Click to expand...
Click to collapse
You should do the oreo version, if your were on the global oreo ROM. After that you can try the pie version, if nothing works don't worry you can do a backup of your data from twrp to your computer and flash a custom ROM or the chinese Pie version, which is recommended. With root access you can easily debloat the chinese ROM and with AdAway you can disable all communications pointing to chinese servers or websites. I also found these. Maybe you can give them a try.

After a few hours I was finally able to install the "Chinese stock rom", although I struggled, since the files of the "rom" of the l58041 do not quite coincide with the "stupdroid" tutorial and some files have two different versions, something like that:
here I chose the "ddr" .
prog_emmc_firehose_xxxx_ddr.mbn (.elf). prog_emmc_firehose_xxxx.lite.mbn (.elf).
here I chose the "retain_userdata".
rawprogram0.xml. rawprogram0_retain_userdata.xml.
and in qfil "Flat Build", however I don't know if it was the right thing because at the beginning I was asked for a password ("but that's another topic").
To add a language (without root), use local more apk.
"https: // c. mi. com / thread-2098669-1-0.html"
To root the "radiationofthenation" thread worked me.
"https:. //forum .xda-developers . com/general/help/lenovo-s5-pro-root-global-firmware-help-t3895643/page2"

kcire_eae said:
After a few hours I was finally able to install the "Chinese stock rom", although I struggled, since the files of the "rom" of the l58041 do not quite coincide with the "stupdroid" tutorial and some files have two different versions, something like that:
here I chose the "ddr" prog_emmc_firehose_xxxx_ddr.mbn (.elf). prog_emmc_firehose_xxxx.lite.mbn (.elf).
here I chose the "retain_userdata" rawprogram0.xml. rawprogram0_retain_userdata.xml.
and in qfil "Flat Build", however I don't know if it was the right thing because at the beginning I was asked for a password ("but that's another topic").
To add a language (without root), use local more apk.
"https: // c. mi. com / thread-2098669-1-0.html"
To root the "radiationofthenation" thread worked me.
"https:. //forum .xda-developers . com/general/help/lenovo-s5-pro-root-global-firmware-help-t3895643/page2"
Click to expand...
Click to collapse
I'm glad it is working for you now. Yes, you are right the tutorials flap at some points, but there are other tutorials which you can follow and make it work. For the first time I was struggling with the restoration, too. You will see, that the chinese ROM is quite good, you just have to uninstall the bloatware and disable spying DNS requests.

Halwer said:
I'm glad it is working for you now. Yes, you are right the tutorials flap at some points, but there are other tutorials which you can follow and make it work. For the first time I was struggling with the restoration, too. You will see, that the chinese ROM is quite good, you just have to uninstall the bloatware and disable spying DNS requests.
Click to expand...
Click to collapse
Ohh, explain more about spying. And also if you know something about the message that Android told me when I start. I remember that I flashed twrp.img using "fastboot", and when I asked for a password to decrypt, it only allowed me to clear cache and dalvit cache (I did wipe), and when I started again I showed a message saying that I was encrypting and a percentage, just here, I interrupted the process by turning off the cell phone, and flashed again with qfil (download). So when I start I just remember that I said something about the cell phone being restored and then I could restore the copy with my Google account. So what I think is that when the message of "TO START ANDROID ENTER YOUR PASSWORD" is displayed, it may work to interrupt or perhaps to put the incorrect password many times to automatically reset or also choose "rawprogram0.xml" in qfil (but I did not dare because it deletes it the information related to the imeil and the signal or at least that says some comments ). Now there is only one who can interpret what happened and to have clearer the restoration process, the rom seems to me very much the problem of the language is solved with "more local", I am from Mexico (At & t).

good morning i have good new
i have been backing up the global rom
just wants to go a long time it is super compressed 3.5giga and it is regular size 10.6 g

nikosddesign said:
good morning i have good new
i have been backing up the global rom
just wants to go a long time it is super compressed 3.5giga and it is regular size 10.6 g
Click to expand...
Click to collapse
Thank you, I'm sure some people will find it very useful!

Hello
it's about 4gigabyte have to be patient.
i have very bad internet connection...