Hello everyone ,
so , I've been this and here is what i did to get back to normal :
1- download MiFlash and the oreo 8.1 (V9.6.8.0.ODHMIFE) fastboot image from here
2- download *adb* file that i upload , and extract the files
3- download this file ,and extract the files , you will find *TWRP* folder
4- copy or move *adb* folder to the C:\
5- use Miflash to flash the fastboot image
6- when your phone start bootlooping go to the fastboot in the phone
7 - open the *adb* folder and run *Command Prompt* , write *fastboot boot recovery.img*
8- when the TWRP start go to pc and copy *TWRP* folder and place it in the main internal
9-go to restore in TWRP and chose the backup folder , restore *Boot* and *EFS* and swipe (if it doesn't show anything to restore go to TWRP>backup and copy *2018-12-06--15-41-27_PQ1A181205006* folder into *TWRP* folder "not to backup folder")
10- now in TWRP go to reboot and click bootloader
11- you will go to fastboot , flash oreo 8.1 (V9.6.8.0.ODHMIFE) by MIflash
12- everything will get back to normal !! :highfive:
update (3-10-2019) :
i recommend to flash latest official mi a1 rom maybe well fix it (using fastboot) ,
any way here is new link for TWRP file http://www.mediafire.com/file/j6682qbs7qa5sg5/TWRP.7z/file
thanks to :
@joeyhuab for the advice
@berlin51 for the link
@abhishek987 for the recovery image file
So this will not mess up any IMEIs or anything? Is this a universal solution for everyone who messed up?\
EDIT: Nevermind, used the guide, works fine. Thanks for that!
It's working. Thank you!
Just need to copy "2018-12-06--15-41-27_PQ1A181205006" to TWRP folder.
following the tutorial, but my sim card didnt work, any solution?
adnbwta said:
following the tutorial, but my sim card didnt work, any solution?
Click to expand...
Click to collapse
IMEI must've got corrupted
Dail *#06# and check if it is showing phone's IMEI numbers n not zeroes
UCFour said:
IMEI must've got corrupted
Dail *#06# and check if it is showing phone's IMEI numbers n not zeroes
Click to expand...
Click to collapse
imei still there, both sim, but in settings-imei SV both are 00, anyway to fix it?
adnbwta said:
imei still there, both sim, but in settings-imei SV both are 00, anyway to fix it?
Click to expand...
Click to collapse
SV values are zeroes by default
Try to flash the same fastboot rom again but this time via EDL mode [ fastboot oem edl] using miflash
UCFour said:
SV values are zeroes by default
Try to flash the same fastboot rom again but this time via EDL mode [ fastboot oem edl] using miflash
Click to expand...
Click to collapse
Can you explain a bit
Sent from my OnePlus5T using XDA Labs
If anyone is planning to flash Pie stable/beta
1. First take a backup of EFS from TWRP and Low level backup of all partitions ( system n data not needed ) with low level backup tool via EDL
2. In order to get Pie booted, you just need "System.img" extracted from the OTA ( use payload dumper) or just take the system.img file floating around here
3. Transfer System.img to adb folder >> Boot to fastboot and flash the system.img only
fastboot flash system_a system.img
fastboot flash system_b system.img
Everything works except dual 4G/VoLTE
Downgrade will also won't have any issues
> For Dual 4G/VoLTE, you also need to flash modem and rpm
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img [ Optional]
But now if you try to downgrade , you might end up with bootloop
>> To Fix bootloop, boot to EDL
Flash the fastboot rom you were running before when you took back of partitions
Then Use lowlevel backup tool to restore all the partitions and reboot
---------- Post added at 08:38 PM ---------- Previous post was at 08:35 PM ----------
Amanpreetsingh said:
Can you explain a bit
Sent from my OnePlus5T using XDA Labs
Click to expand...
Click to collapse
Procedure is same as flashing fastboot rom via EDL mode with MiFlash but instead of flashing it from fastboot try it from EDL mode
Use this command within fastboot mode to get to EDL
fastboot oem edl
Total process will take 10+ minutes, once the flashing status changes to "Success", hold the power button for around 10 seconds to reboot
UCFour said:
SV values are zeroes by default
Try to flash the same fastboot rom again but this time via EDL mode [ fastboot oem edl] using miflash
Click to expand...
Click to collapse
done that, but the sim still not showing, tried to swipe sim to slot 2 but no change, really confused right now
adnbwta said:
done that, but the sim still not showing, tried to swipe sim to slot 2 but no change, really confused right now
Click to expand...
Click to collapse
Check if those IMEI numbers are your phone ones only? AFAIK EFS is device specific which contains information like IMEI, MAC Address..
UCFour said:
Check if those IMEI numbers are your phone ones only? AFAIK EFS is device specific which contains information like IMEI, MAC Address..
Click to expand...
Click to collapse
both IMEI in the settings and in the box are the same, but now after flash image from EDL both IMEI become 0 and unknown, any solution?
adnbwta said:
both IMEI in the settings and in the box are the same, but now after flash image from EDL both IMEI become 0 and unknown, any solution?
Click to expand...
Click to collapse
Use this guide
https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190
1. Download 7.8.23 Nougat Fastboot rom, flash it via EDL
2. If the phone boots fine to OS, Great! [ IMEI fix only possible with Nougat ] else restore the EFS again via TWRP [ Don't restore anything else modem/boot] to get the rom booted
3. Download Qualcomm dailog driver, IMEI to Hex converter, HEX Editor and QPST tool [ Latest ]
4. Open IMEI to HEX Converter, inpur your IMEIs and save the hex numbers somewhere else
5. Now download the QCN file linked in this post, open the QCN with hex editor and navigate to the address locations 0x17C50 & 0x02530 and replace the hex values "08 8A 16 11 11 11 11 11 11" and "08 8A 26 22 22 22 22 22 22" with the ones you saved before and save the QCN file [ You can can .qcn extension if this file doesn't work in the final step ]
https://forum.xda-developers.com/showpost.php?p=76496159&postcount=23
5. Now type *#*#717717#*#* , you will see dialog port enable status
6. Connect phone to PC, enable Dev options and USB Debugging
7. Open QPST [ Software Download ], Restore Tab see if the port is showing. If it isn't update the driver within device manager
If the port isn't showing even after driver update, detach the phone USB and re-connect phone
8. with the Com port displayed, select browse under xQCN file tab and the select the QCN file u modified with your IMEI numbers
9. Select "Allow ESN Mismatch" and hit start >> wait until status changed to memory process done successfully (something similar)
10. Reboot phone and everything will be fine
After everything is done, first its better to update to Oreo via OTA first [ Two 1GB Updates ] and then flash oreo fastboot rom
UCFour said:
If anyone is planning to flash Pie stable/beta
Click to expand...
Click to collapse
Is that for people who flash it through fastboot or is this required if we update to the stable through OTA as well?
michkost858 said:
Is that for people who flash it through fastboot or is this required if we update to the stable through OTA as well?
Click to expand...
Click to collapse
There is no official fastboot rom yet, the one available has the contents of extracted payload.bin from the OTA
Even if you update your phone via official stable OTA, you will be facing same downgrade issues
Yeah i meant it for those who are planning to flash via fastboot as most OTA users with locked bootloader wouldn't bother to downgrade
Please help me I did the steps and manages to restore the stock rom, but I get a message saying "phone not allowed" And when I want to make a call tells me "mobile network not available "
UCFour said:
Use this guide
https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190
1. Download 7.8.23 Nougat Fastboot rom, flash it via EDL
2. If the phone boots fine to OS, Great! [ IMEI fix only possible with Nougat ] else restore the EFS again via TWRP [ Don't restore anything else modem/boot] to get the rom booted
3. Download Qualcomm dailog driver, IMEI to Hex converter, HEX Editor and QPST tool [ Latest ]
4. Open IMEI to HEX Converter, inpur your IMEIs and save the hex numbers somewhere else
5. Now download the QCN file linked in this post, open the QCN with hex editor and navigate to the address locations 0x17C50 & 0x02530 and replace the hex values "08 8A 16 11 11 11 11 11 11" and "08 8A 26 22 22 22 22 22 22" with the ones you saved before and save the QCN file [ You can can .qcn extension if this file doesn't work in the final step ]
https://forum.xda-developers.com/showpost.php?p=76496159&postcount=23
5. Now type *#*#717717#*#* , you will see dialog port enable status
6. Connect phone to PC, enable Dev options and USB Debugging
7. Open QPST [ Software Download ], Restore Tab see if the port is showing. If it isn't update the driver within device manager
If the port isn't showing even after driver update, detach the phone USB and re-connect phone
8. with the Com port displayed, select browse under xQCN file tab and the select the QCN file u modified with your IMEI numbers
9. Select "Allow ESN Mismatch" and hit start >> wait until status changed to memory process done successfully (something similar)
10. Reboot phone and everything will be fine
After everything is done, first its better to update to Oreo via OTA first [ Two 1GB Updates ] and then flash oreo fastboot rom
Click to expand...
Click to collapse
i follow the tutorial, but the imei in phone is different with the one in the box, maybe I did something wrong in step 5, can u tell me how to change or remove imei?
adnbwta said:
i follow the tutorial, but the imei in phone is different with the one in the box, maybe I did something wrong in step 5, can u tell me how to change or remove imei?
Click to expand...
Click to collapse
If the IMEI is different then u haven't edited the QCN correctly
Flash Nougat firmware again via EDL
and this time edit the IMEI hex values correctly in the qcn file via hex editor
Also make sure u have converted your IMEI to hex values
for me nothing is showing in twrp folder in restore
pls help
i folled the steps in op properly
---------- Post added at 06:24 AM ---------- Previous post was at 06:01 AM ----------
jai krishna said:
for me nothing is showing in twrp folder in restore
pls help
i folled the steps in op properly
Click to expand...
Click to collapse
I took my own backup of boot and efs.so one folder created in twrp folder.
i replaced my files with the downloaded files given in op
thanks a lot.love u all
I have a question, I am on Android P official BETA flashed with TWRP. I have backed up my previous P PE ROM with Boot, EFS, Persist, Modem full Nandroid Backup. Can I flash official P STABLE (Fastboot ROM) with MiFlash Tool when its available?? Without bricking my device??
Related
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
The BLU VIVO XL4 has arived.
Sorry this guide is not for very new users, it relies on certain amount of prior knowledge.
**NOTE**
Unlocking Bootloader WILL set warranty flag to "NO"
Make the read-back backup, BEFORE unlocking, so there is a possibility to restore warranty to "yes"
Getting SPFlash Tool to work on BLU VIVO XL4
I used sp flash tool version 5.18.28
Needs custom DA file and Auth file. Both have been found from a near clone device.
Open flash tool select the DA file and Auth file from the link below.
add the scatter file from archive. There is a preloader file in the archive also. This is needed for spflash tool to open the Auth file.
Stock Rom and Auth file
Then follow the guide found on youtube.
Not planning to go into too much detail about the actual pulling of the firmware, as there is already
a fantastic guide with step-by-step photos and also a video.
Just the basics
Pull stock rom with spflash tool once just from the "boot region" to get the preloader file.
Process that file with the Wwr_MTK tool to get partition table information.
And one more time pull as one large binary file from the "user region" then split it into
individual images using the tool called "Wwr_MTK" it can be found on other site(Hovatek). I cannot put a
link as it is against forum rules (no advertising other forums)
But there is a youtube video that describes the process. And gives link for download of the tool.
**NOTE-1**
The Wwr_MTK tool did not have the correct chip (mt6762 In fact the "family class" for the chip is mt6765) as an option. Because of this you will need to add it to the tool before using it. Open the downloaded zip.( I used "WwR_MTK_2.40_Eng" ). Open "Template.ini" with text editing software, in the section labeled "CPU" add "MT6765 2" , keep same format as the rest of the file. Save the changes and close Template.ini.
Now when you run the tool, you will be able to create the scatter file as you split the rom into files.
**NOTE-2**
The tool connects to internet and downloads fresh the files and scripts when you start it. There is a 30 second ad screen displayed. If you block internet to the tool, then the add screen turns into 2 minute wait screen. I am not suggesting that you hack the tool to by-pass it, just letting you know what to expect.
IT IS HIGHLY RECOMMENDED TO MAKE YOUR OWN FULL BACKUP BEFORE PERFORMING THESE STEPS
AFTER YOU HAVE MADE FULL BACKUPS
Now to start modifying
DOWNLOAD
UNLOCK BOOTLOADER
unlocking bootloader is no more complicated then then enabling OEM unlock toggle in dev options menu.
Then performing Command in terminal. Just like so many android devices.
Unlock Bootloader
1. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select more "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
2. Open cmd or power shell terminal
3. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
4.Once the phone has finished loading into fastboot mode type this command
Code:
fastboot oem unlock
I also did --MIGHT be an optional step
Code:
fastboot flashing unlock
Do not think both were needed.
After each command when phone was rebooted,
it took extra time to open. But did not show the normal recovery screen while
it did the factory reset. But a reset did happen both times,
as I had the setup wizard each time.
Even after unlocking bootloader, doing a "fastboot boot *xyz.img" (boot or recovery test images)
Phone would only cycle to off then do a full reboot. Doing "fastboot flash boot boot.img" does flash the boot.
And "fastboot flash recovery recovery.img" does flash the recovery.
TWRP
1. Download TWRP From Link above
2. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
3. Open cmd or power shell terminal
4. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
5. Now give the command to flash twrp, assuming you downloaded the file to default download folder
Code:
fastboot flash recovery %userprofile%\downloads\TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img
5. Reboot to twrp. Needed to boot directly to twrp, or stock recovery will be re-flashed by phone.
Code:
fastboot oem reboot-recovery
Once inside twrp It is asking for password to unlock (decrypt)***automatic decrypt not work on this device as of YET***
this is supposed to be same password used to unlock phone.
Because this twrp does not work with encryption, every time you reboot you will have to select language, if changed from default.
To get recovery to be functional, you need to make phone patched for both "DM-Verity" and "Force-encryption"
I do this with
"Universal Disabler"
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
There is similar utiliy built into this Recovery image.
to use the built in option , Select ADVANCED, Then RM Forceencrypt
This will flash the lazypatcher with options set to remove encryption both in boot.img and /vender/*fstab : remove dm-verity.
--OR-- manually do the following steps
Steps
1. Download Zip from Link above.
2. Open TWRP
3. Open Wipe menu
4. Select format /data
5. Key in "YES" and swipe
6. Return to Home Page of TWRP
7. Choose reboot menu then recovery
8. Recovery should now have access to Internal memory (temp for now)
9. Use abd push to put the zip file downloaded above to internal memory
Code:
adb push %userprofile%\downloads\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip /sdcard/
10. Select install menu , and install the Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip
Do not rename the file. It installs and makes the patch base on the file name.
If you want to have root also, then flash Magisk at this point.
Now the dm-verity and force encryption are off. You can flash gsi custom rom, if you desire. At the moment, I have only been able to boot the phone with working cell data and calls on the PHH-Phusion --vanilla builds. Do not know why the gapps versions do not allow rill to function.
As of the writing of this I have put up V4 of the TWRP port. This version uses the correct mount points for this phone, not the ones from the source of the port. Also corrected the device name in default.prop, to match device name. Build fingerprint has been left as is. Fixed the micro sdcard name and OTG names. Added mipe to the "misc" /"para" partition to escape a factory reset recovery loop that [uu]could[/u] happen under certain situations.
And my prefered ported recovery from LRTeam TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img.
DOWNLOADS
Files
1. Sp Flash tool (v 5.18.28 or newer) https://androidmtk.com/smart-phone-flash-tool
2. stock XL4 ROM, DA file, TWRP all in shared folder https://androidfilehost.com/?w=files&flid=287088
3. stock Xi+ ROM, TWRP in shared folder https://androidfilehost.com/?w=files&flid=287703
4. Unviversal DM-Patch disable tool thread
5. Youtube Guide Video to use backup image splitter tool "WWR_MTK" https://www.youtube.com/watch?v=GMAytZ56hac
Kernel sources have been published 12-12-2018, by BLU
I have them synced to GitHub while I make test builds.
https://github.com/mrmazakblu/BLU-VIVO-XL4-kernel
Default defconfig should be arch/arm64/config/k62mv1_64_bsp_defconfig. Based off of build description in "getprop"
Built kernel has not been able to be booted yet.
TWRP is first ported and provided thanks to @Voinea12
.
placeholder not really welcomed here on XDA
just pm a moderator or report this thread when you`re ready to upload something, until then, thread closed
After seeing that the Blu vivo xl4 requires an "auth file" in order to flash with spflash tool, I asked BLU to supply the file.
They responded with a big fat NO.
.......
.......
THE NEXT DAY THE FILE WAS POSTED ON A DIFFERENT THREAD.
SO THERE HELP WAS NO LONGER NEEDED.
Just made successfull readback on preloader. and currently reading full rom.
will post link when done.
here is auth file and DA file I used.
pulled firmware is here.
there are more images in complete firmware, but the ones included should be enough , as long as you NEVER do format all from spflash tool.
STOCK ROM
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Working version is available now
Thread was opened.
mrmazak said:
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Click to expand...
Click to collapse
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
psychofad said:
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
Click to expand...
Click to collapse
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
mrmazak said:
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
Click to expand...
Click to collapse
No, I got the readback of the EMMC_USER just fine and ran it through the WwR MTK tool and it gave me the hex address to use for the full rom readback, t then told me
Code:
The file size is smaller than the start position of the LK (uboot). To determine the type of processor and memory, it is necessary to read the full firmware in the SP Flash Tool, specify the parameters for reading: Start address: 0x0, Lenght: 0x1D1EC00000.
So I entered those two addresses as EMMC_USER readback. If my phone is off and I just connect it to the usb without holding any keys it gives me another error.....and I'm an idiot. just figured it out as I was looking at logs, apparently I must have changed the usb speed in sp flash which changes it's pid causing it to try and read from another port. It's downloading now
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
******EDIT*****
Most of the following problems did not repeat in same way when I tried to repeat the install process.
Main issue was with simcard. But exact process to get installed and working is still not known.
-- install after already having rooted, encryption removed stock, seems to work.
-- fresh full stock rom, full encryption, then gsi seems to not work sim card.
PHH-treble gsi images do boot this device. I do not have a bug list as yet.
working:WITH encryption removed:
1. wifi
2. camera
3. fingerprint- unlock
4. music
5. video
NOT working :WITH encyyption removed:
1. cell signal
2. cell data
3. phone
4. sms
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------
working:WITH encryption enabled
1. phone
2. sms
NOT working:WITH encryption enabled
1.. everything else
EDIT
Much of the force closing problems were from a corrupted external sdcard. When I removed the card , the force close messages did not come.
Getting 4G data connection was not stable. after a full reset and rom re-install I was not able to get data connection, and only able to have connection to make calls when set to 3G connection only.
some bugs in vendor I assume will need some help solving this.
EDIT 2
Finally got around to trying again. his time I started with vanilla version of phh-treble gsi.
4G data and sms, calls in out all work. Camera , video both work.
WiFi tethering did not work.
Setup that worked :
force encryption removed with universal dm-verity patcher, ( bothboot.img and vendor partitions both edited).
magisk patched boot
Would this work on Blu Vivo XI since same chipset?
sinkoo1979 said:
Would this work on Blu Vivo XI since same chipset?
Click to expand...
Click to collapse
It should. I have been working with few users with Xi+ it works for them. And another user of Xi provided a twrp port, but no details on if this read-back worked. It must have, I suppose it must have.
Please do try to do the readback for your self, and share the files. will help with twrp if I can
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
mrmazak said:
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
Click to expand...
Click to collapse
Can any of this be done without a computer
Decaphyz said:
Can any of this be done without a computer
Click to expand...
Click to collapse
No, you need fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
mrmazak said:
No, need you fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
Click to expand...
Click to collapse
Oof
mrmazak said:
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
Click to expand...
Click to collapse
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
IndifferentBear said:
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
Click to expand...
Click to collapse
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
thanks dude! can you give me the command to run in terminal to do it? ill try that first, then ill try flashing stock recovery!
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
but i was required to wipe the sys, data, cache, and dalvik/art to have a clean install.
---------- Post added at 03:33 AM ---------- Previous post was at 02:47 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
YO! Oaky so basic laly when i flashed that misc recovery IT BOOTED!!!!! thank you soo much dude, your the best!
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
This is Generic guide for Unbricking or Downgrading Huawei devices with Kirin 960 CPU. Most probably very similar steps can be done for Kirin 970, but i don't have device to test. At the end i did attach my files, that i used for CMR-W09.
This WILL WORK even if you have Black Screen with permanent Fastboot - this is common issue for those, who tried to downgrade from EMUI 9 to EMUI 8. Yes, this is also unbrickable!
Have Fun!
1. Prerequisites
- Linux installed on your PC/laptop or as Virtual Machine, with fastboot tool on it
- Board Software for your device – you can find on easy-firmware.com (about $15 for pass and reach collection) or gem-flash.com (has cheap $3 pass but less firmwares in collection)
HiKey_IDT linux tool – can be found there https://github.com/96boards-hikey/tools-images-hikey960/
- Knowledge about test point location to interrupt CPU loading routine – ask google or look on this forum
http://forum.gsmhosting.com/vbb/f1022/huawei-test-point-gallery-2291781/index17.html
- Opened device – you need access to motherboard
2. Booting device in force update mode
Small intro. Hisilicon Kirin CPUs has special mode, when they are interrupting normal boot process and opening COM port on USB to accept commands. You have chance to load your own binaries directly to device RAM before boot process will continue (still, this images has to be signed by Huawei private key)
- Disconnect battery connector from motherboard
- Short test point to ground (any big metal shield on board will work for that)
- Having test point shorted – connect USB cable. Run “lsusb” command – you should see device “USB SER” in devices
- Open folder with Board Software. Find xml file with model name in name, for ex. “CMR-W09-BD_1.0.0.19_Download.xml”. In that xml file – check section for “bootloaderimage” – you will find paths and memory addresses for all needed boot stages. Keep that open.
- Find all three boot img files – copy them to Linux machine. Note: For me, this three files didn’t work. But I found files with same names in other folder of Board Software – and that did a trick. You have to experiment a little bit.
- Go to folder, where you have HiKey_IDT tools downloaded. Copy three boot files from Board Software to same folder as hikey_idt. Edit “config” file – you should specify correct address and file name – according to Board Software
- Check “dmesg” command output – look for GSM Modem connected messages – you will see port name attached – like ttyUSB0
- Run next command “./hikey_idt -c config -p /dev/ttyUSB0”. You should see information about loaded all boot stages, with “Finish downloading” message after each. If you did everything fine – in 5-15 seconds you will have your device ready for downgrade/unbrick/killing_your_cat
- To verify that everything is fine – run “fastboot devices” command. If it will show device with proper serial number in output – you are fine to continue
3. Fixing your device
On that step – you have special fastboot booted, that has no security/validation on it. You can unbrick your device, or kill it. Do all steps carefully.
- Flash proper partition table information. You can take it from OTA package (from inside of UPDATE.APP) – normally, it has name HISIUFS_GPT. Run “fastboot flash ptable HISIUFS_GPT.img”
- Flash other partitions one by one. Skip files CRC.img, SHA256RSA.img, CURVER.img, VERLIST.img, PACKAGE_TYPE.img and HISIUFS_GPT.img (it was already flashed on previous step). To flash this files, run “fastboot flash” with partition name and image file name after it – for ex. “fastboot flash recovery_vendor RECOVERY_VENDOR.img”. Note: Partition names should be written in lowercase. You can see partition names in Huawei Update Extractor, as extracted image files sometimes has shortened names.
- Run few more commands to cleanup things around:
Code:
fastboot erase misc
fastboot erase modemnvm_factory
fastboot erase bootfail_info
fastboot erase dfx
fastboot erase rrecord
fastboot erase patch
- Flash few more files – from Board Software:
Code:
fastboot flash splash2 splash2.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot erase version
fastboot flash version version.img
fastboot flash reserved4 gpu_test_data_all_v2.bin (may be different for other devices – look into XML file from Board Software package for any “reserved” partitions)
- Remove USB cable, connect battery back and boot your device. Most probably your device will boot now! Or at least it will try
4. Final steps
- Make factory reset from stock recovery!
- Make 3-button flash of same or newer firmware just after restoring device!
- Make backup of your NVME and OEMINFO! Use next commands for that:
Code:
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/storage/emulated/0/oeminfo.img
dd if=/dev/block/bootdevice/by-name/nvme of=/storage/emulated/0/nvme.bak
Above commands are for adb shell with root. If you will do that under TWRP – you can use “of=/sdcard” in dd commands
Note: If your device is in bootloop, but runs recovery/eRecovery fine. If recovery is showing error during factory reset – maybe, you have screwed your nvme during previous upgrades/downgrades. In that case – make NVME backup using TWRP, take nvme.img from Board software package. Using any HEX editor – open both files, and copy all variable values from your backup to nvme.img from Board – manually. After doing that – repeat all steps from beginning until getting forced fastboot mode, and flash this image with “fastboot flash nvme”
P.S. In above links you may find lovely-prepared files for CMR-W09 tablet with region C432 for recovering to b161 firmware (includes recovery.sh script to flash everything in one command) - it can be used to get $4 unlock code with DC Unlocker.
HiKey_IDT => https://drive.google.com/open?id=1EdNfHVc8japoVSe2k4iTWdyp5JyPa1LR
Recovery Files for CMR-W09 C432 B161 => https://drive.google.com/open?id=1YgwwwFITjbJ8vIepcCt0O5w_RRJcKV8F
Board Software for CMR-W09 => https://drive.google.com/open?id=1w3mfVt8ObsViiv5ov3cUAog-M8hHMaSF
Testpoint location on Mediapad 10.8 (should be same on both Pro and non-Pro)
Reserved
Damn! I sent my tablet to a repair center two days ago...
Thank you for this great guide!
crckmc said:
Damn! I sent my tablet to a repair center two days ago...
Thank you for this great guide!
Click to expand...
Click to collapse
Nah, i'm not looking for fast ways! Decided that i can do it by my own ))) Btw, service center will not even try to repair your tablet - they will replace whole logic board or whole tablet.
For me It gives errors, I used my own device board fw.
Which device do you use? Did you boot it with testpoint?
If it is any of M5/M5 Pro (even if it is 8.4") - you can use files that i attached - hikey_idt is preconfigured. For other kirin960 devices that may need different boot files from own board
goodwin_c said:
Which device do you use? Did you boot it with testpoint?
If it is any of M5/M5 Pro (even if it is 8.4") - you can use files that i attached - hikey_idt is preconfigured. For other kirin960 devices that may need different boot files from own board
Click to expand...
Click to collapse
Booted with testpoint, and I used the Huawei P10 (It's a kirin960) and used my own boot files from the board fw. From what I know, I did a wrong downgrade, I did not know about the xloader thing going on, I had B386 installed, and tried do downgrade to B369a, different xloaders both of them. Now the screen is black, can't get into fastboot this way, I used DC-Phoenix too, managed to get somehow into fastboot, but these flashing errors still happened saying partition lenght get error, my logicboard may be already damaged tho.
yoghurt13 said:
Booted with testpoint, and I used the Huawei P10 (It's a kirin960) and used my own boot files from the board fw. From what I know, I did a wrong downgrade, I did not know about the xloader thing going on, I had B386 installed, and tried do downgrade to B369a, different xloaders both of them. Now the screen is black, can't get into fastboot this way, I used DC-Phoenix too, managed to get somehow into fastboot, but these flashing errors still happened saying partition lenght get error, my logicboard may be already damaged tho.
Click to expand...
Click to collapse
But the first - try hikey_idt with my files (it is preconfigured in attached archive). If it will be still throwing errors (i had same errors with wrong boot files) - take own files from your board. But not from "bootloaderimg" or "fastbootimage" folders - i got success with files from "update_nv_bootloader_block" folder of my board software package.
Next step - after you will boot board with hikey_idt and willl have fastboot loaded (screen will be still black - this is normal) - you will have to write partition table to device eMMC. For that - extract HISIUFS_GPT.img from UPDATE.APP and flash it as "ptable" - run "fastboot flash ptable HISIUFS_GPT.img". If that will go without errors - you can flash other images one by one.
What linux should i have? It's not possible under windows?
lukastob said:
What linux should i have? It's not possible under windows?
Click to expand...
Click to collapse
Any distro that you like - will work for you. If you are newbie - you can take Ubuntu for ex. Also, virtual machine with linux will be totally fine - just you should check everytime that USB is passed from host to VM. And no - i don't know about alternative tool for hikey_idt under WIndows, and service version of IDT - is bad-bad-bad. So, Linux is your choice.
Good jobs man ))) thanks from all users for testpoint
Well I managed to get into the special fastboot, and I could flash a few thing, but at least 5 images fail the verification, including Xloader, It's strage, as the Xloader still tries to verify things.
yoghurt13 said:
Well I managed to get into the special fastboot, and I could flash a few thing, but at least 5 images fail the verification, including Xloader, It's strage, as the Xloader still tries to verify things.
Click to expand...
Click to collapse
Try to flash xloader from OTA, not from board. From UPDATE.APP. Did you flash ptable in that mode?
goodwin_c said:
Try to flash xloader from OTA, not from board. From UPDATE.APP. Did you flash ptable in that mode?
Click to expand...
Click to collapse
I was doing that, I tried the ota xloader, and I tried the board sec_xloader too, they did not work, both of them has verification errors. Flashing DTS, fastboot, trustfirmware gives this error FAILED (remote: 'image verification error'). And yes, I flashed the Ptable too.
yoghurt13 said:
I was doing that, I tried the ota xloader, and I tried the board sec_xloader too, they did not work, both of them has verification errors. Flashing DTS, fastboot, trustfirmware gives this error FAILED (remote: 'image verification error'). And yes, I flashed the Ptable too.
Click to expand...
Click to collapse
from which folder did you take boot files for hikey_idt? maybe, you could try to take older board firmware? Or try to flash files from "fastbootimage" folder of your board.
goodwin_c said:
from which folder did you take boot files for hikey_idt? maybe, you could try to take older board firmware? Or try to flash files from "fastbootimage" folder of your board.
Click to expand...
Click to collapse
I literally have only 1 board firmware version the VTR-AL00, and I tried those stuff already, only your hikey-idt preconfigured got it into fastboot, after that I tried to flash my own board fw stuff onto it. So this whole thing might not work in my case.
yoghurt13 said:
I literally have only 1 board firmware version the VTR-AL00, and I tried those stuff already, only your hikey-idt preconfigured got it into fastboot, after that I tried to flash my own board fw stuff onto it. So this whole thing might not work in my case.
Click to expand...
Click to collapse
Can you share somewhere files from your board? i'll look into it.
goodwin_c said:
Can you share somewhere files from your board? i'll look into it.
Click to expand...
Click to collapse
Yeah, I'll upload the thing, I'll PM you the link.
Okay, I somehow managed to get it to work, found the perfect rom for the reset, BUT, the thing is, I lost my IMEI number from the phone, is there any way to reset it?
Amazing, thank you for this
---------- Post added at 10:02 PM ---------- Previous post was at 10:00 PM ----------
yoghurt13 said:
Yeah, I'll upload the thing, I'll PM you the link.
Click to expand...
Click to collapse
I think because of the relocked bootloader
Hi
in this thread i will show you how to do each of this:
POCO X3 PRO{vayu}
1.TWRP+ROOT
2.RSA DISABLE
3.DIAG MODE
4.EFS RESET
5.IMEI REPAIR
without Any Box.
----------
***********You Will Do it By Your Responsibility and I'm not Responsible for any damage to your Device,Read Thread Carefully and then Do it and try not to mess your device*********
--------
Requirements:
-Iphone 6 Board for its Resistor
-Xiaomi Imei Tool Link
-Qpst Link
-Twrp + EFS Reset Tool Link
-Magisk 23 zip file Link
-Magisk Manager APP Link
-Stock Firmware Link
-Eng Firmware LINK >>>>File Password is : iaasteam.com<<<<<<
--------
I Did All of this Steps and Job Done this Means Its Tested dont Blame me For Any Damage to Your Device
Do it Just if you know What you Do
Not for Newbies
---------------
Some Poco X3 Pro Devices Bootloop After EFS Reset:
it can caused Becuase of Firmware Security or RSA Encryption of Device Imei:
We Have Two Method For this:
1.Flash ENG Rom Then Continue The Steps 1 to 4 and no need root(Because ENG rom have root access already)
2.Do entire Steps on stock Firmware then if it gives error try method 1
But if Not if this methods Work Problem is with the Step 1.RSA DISABLE and you should Check You Resistor
---------------
1.RSA DISABLE
You Should Disable RSA of the Phone To Write Imei on it.
For this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Remove this resistor and Change it with Picture 2 from Iphone 6 Board 50k resistor
for better Performance of work you can Measure its kohm by ohm meter it should be 45 to 50k by ohm meter
replace the resistor in picture one with this
------------
First Time We do entire of Job on stock Firmware if firmware security Prevent us to do our work then we flash the phone with eng firmware,and eng firmware no need root just need flash twrp
-----------
2.TWRP + ROOT
Download Reqirment TWRP + EFS RESET TOOL
Reboot phone in fastboot and connect it to pc
run .bat file and press key 1
twrp will be flashed
Wipe/factory reset Phone by twrp if storage not shown for installing packages reboot agian to twrp
Download Magisk zip and Apk from reqirement
****Go to Backup Section of TWRP>Check EFS Partition>Back it up and Copy it to PC for Avoid Baseband null***** And then Continue the other Steps
Connect Phone to pc
Copy Magisk23.zip to phone storage and install it by twrp
Reboot phone to system
and install Magisk Manager
Now phone Should Be Rooted.
Each time you reboot your phone from Recovery to system,TWRP recovery will be deleted onm your phone
when you see your phone rooted
----------
3.DiagPort & QCN Backup & Modify
Download QPST in reqirement
Xiaomi Imei Tool in reqirement
Install Xiaomi Imei Tool
View attachment 5515295
Connect phone to pc in normal Mode
Enable USB Debugging and Select File Transfer mode on phone
Click Open Diag Port now your diag prot enabled
***** Do not use Xiaomi Imei tool QPST******
Install QPST from Reqirements Section
Run QPST Configuration(you can search in start menu for it Because it dont have shortcut in desktop)
QPST Configuration Detect Your phone in diag mode then
Click on Start Clinets>Software Download>Backup
Backup QCN And Xqcn Both(QCN is enough but I suggest you to backup both of them)
when you backed up Qcn
Open Xiaomi Imei Tool
And run QCN Editor
View attachment 5515301
1.select Qcn file you Backed Up
2.Select Registration Method on 2Sim Like in picture
3.Write Imei 1 and imei 2
4.Click Create Button and Save our Modified QCN.
--------------------
4.EFS Reset And Modified QCN Restore(Imei Repair)
Warning:You should Backed up your EFS By TWRP in STEP 2 and Copied it in PC And Then Come To This Step
Reboot your Phone to Fastboot
-Open TWRP+EFS reset .bat file you downloaded in step 2
-press 1 and wait untill phone reboots to twrp recovery
-in the .Bat File Menu press key 2 when phone already is in twrp menu
-Reboot Phone to system Again Now Efs Reseted and Phone Dont Have IMEI
*******If You Dont Replaced Correct Resistor in Step 1 then your phone should give you NV Data Corrupted Error in this Step or Phone Restarts Each Time********
-When Phone Comes Up Enable Diag port Again and run QPST
Run QPST Configuration(you can search in start menu for it Because it dont have shortcut in desktop)
QPST Configuration Detect Your phone in diag mode then
Click on Start Clinets>Software Download>Restore
Select Modified Qcn that you Created By Xiaomi Imei Tool in Step 3 and Push Start.
Wait Untill Progress Done And Phone Reboots.
Now You Should Have Poco X3 pro Dual Imei Repaired.
If you Get Any Error Just Read Troubleshooting Section
--------------------------------
*****************Troubleshooting****************
1-After EFS Reset Phone Restarts and dont Work Correct
A:it can caused by two problem: 1- firmware security 2-Resistor Change Problem
For Firmware Security:
-Download ENG Firmware From Requirement section and Flash it by fastboot
-then Reboot To Fastboot again Flash Twrp recovery and do not try to root ENG firmware(Because it have Root Access by default)
-In Twrp Reset EFS Again In Step 4
-Reboot to ENG firmware and Enable Diag Port and Write Modified Qcn
-Flash Global Stock Firmware i have linked to requirement no diffrence at all you can flash any version of global firmware
***If Again Problem Not fixed It's your 50k Resistor Changing Problem and you should check it***
2-When I Enable Diag Port QPST Can not find my phone
A:Just Check You Drivers And Device Manager
--------------------------------
*****In Some Websites Says You Need ENG QCN for imei repair,No need of ENG QCN Just Modify Phones Original QCN******
--------------------------------
Files Uploaded To mega.nz and Links Stays Alive forever.
--------------------------------
Push Thanks Button,Like if this Guide fixed your problem
If you have a question, feel free to ask and I will answer as soon as possible
***********You Will Do it By Your Responsibility and I'm not Responsible for any damage to your Device,Read Thread Carefully and then Do it and try not to mess your device*********
I have a question, if I have a Poco X3 Pro with a blank imei and an unknown baseband, I don't have the EFS backup or the box where the imei comes from, changing the resistance and following the step-by-step guide could I recover the imei?
felixpaz1992 said:
I have a question, if I have a Poco X3 Pro with a blank imei and an unknown baseband, I don't have the EFS backup or the box where the imei comes from, changing the resistance and following the step-by-step guide could I recover the imei?
Click to expand...
Click to collapse
if problem not with the hardware
yes of course you can fix it
when you remove resistance and disable rsa
and write its original imei on it.
Any change in the imei ID of the device is illegal in most countries, please respect the law.and Also respect XDA Law about it.
I've reverted the OP and thread title as they were, as well as unlocking it, and will PM all appropriate users.
Thank you.
roirraW edor ehT said:
I've reverted the OP and thread title as they were, as well as unlocking it, and will PM all appropriate users.
Thank you.
Click to expand...
Click to collapse
Thank you, I took the time to write this
Thank you for your positive management
After removing the resistor can it be re-installed?
Jssdje said:
After removing the resistor can it be re-installed?
Click to expand...
Click to collapse
no then rsa enabled again
Non of one of your attachment are available please update the pictures of resistor pic
Thanks
mosirezaei said:
Non of one of your attachment are available please update the pictures of resistor pic
Thanks
Click to expand...
Click to collapse
Hi thank you for report i have uploaded them but now the attachments deleted
wait untill tomorrow i will fix it
dashti.95 said:
Hi thank you for report i have uploaded them but now the attachments deleted
wait untill tomorrow i will fix it
Click to expand...
Click to collapse
Hello
I still waiting for the attachment photos of resistors
if you can send it to my email will be great
[email protected],com
thanks bro
backup efs eng firmware mode .backup was saved fsc,fsg,modemst1 and modemst2. after reset efs baseband unknown. flash backup partition in fastboot mode. still baseband unknown.
problem solved by write qcn.
alak said:
backup efs eng firmware mode .backup was saved fsc,fsg,modemst1 and modemst2. after reset efs baseband unknown. flash backup partition in fastboot mode. still baseband unknown.
problem solved by write qcn.
Click to expand...
Click to collapse
Can you give me the qcn please....
Mail : [email protected]
kallumama said:
Can you give me the qcn please....
Mail : [email protected]
Click to expand...
Click to collapse
tomorrow i will send you
I repair 2nd Imei of Poco X3 pro Vayu from UMT RSA method in eng Rom. I get backup of QCN. it shows imei1 0 imei2 (86*************12) but when I flash global rom. it shows NV data corrupt. I again flash ENG rom. write that backup QCN it shows Original IMEI's but when I flashed Global Rom It shows nv data error again. although Original imei of that Phone. I erase efs from Fastboot that also doesn't help me. what is the problem & how to solve it.
can I flash custom rom for mobile work normally without sim?
or custom rom doesn't help?
if any firmware that solve my problem & phone work normally (without sim) kindly tell me.
saqibsm said:
I repair 2nd Imei of Poco X3 pro Vayu from UMT RSA method in eng Rom. I get backup of QCN. it shows imei1 0 imei2 (86*************12) but when I flash global rom. it shows NV data corrupt. I again flash ENG rom. write that backup QCN it shows Original IMEI's but when I flashed Global Rom It shows nv data error again. although Original imei of that Phone. I erase efs from Fastboot that also doesn't help me. what is the problem & how to solve it.
can I flash custom rom for mobile work normally without sim?
or custom rom doesn't help?
if any firmware that solve my problem & phone work normally (without sim) kindly tell me.
Click to expand...
Click to collapse
1.What Flasher you using to flash data?
2.give me a list of files in your firmware directory please list it for me.
I need to know because:
In qualcomm series of xiaomi phones you have a file named *NON-HLOS*
You should use NON-HLOS file from eng Rom not the original file from global rom.(NON-HLOS file is eng modem file)
give me info i will help you
dashti.95 said:
1.What Flasher you using to flash data?
2.give me a list of files in your firmware directory please list it for me.
I need to know because:
In qualcomm series of xiaomi phones you have a file named *NON-HLOS*
You should use NON-HLOS file from eng Rom not the original file from global rom.(NON-HLOS file is eng modem file)
give me info i will help you
Click to expand...
Click to collapse
I have a doubt in which directory of the ENG Rom I find the NON-HLOS file and if I can back it up, I "install" it in the global Rom, would the QCN written when it was in the ENG Rom work?
dashti.95 said:
1.What Flasher you using to flash data?
2.give me a list of files in your firmware directory please list it for me.
I need to know because:
In qualcomm series of xiaomi phones you have a file named *NON-HLOS*
You should use NON-HLOS file from eng Rom not the original file from global rom.(NON-HLOS file is eng modem file)
give me info i will help you
Click to expand...
Click to collapse
I have followed the guide, I was able to recover the original imei that came in the box, I have changed the 50ohm resistor, when I go back to stock rom I have baseband, I have both imei, but I have no signal, if I want to call a message appears saying "deactivate the airplane mode to call"
felixpaz1992 said:
I have followed the guide, I was able to recover the original imei that came in the box, I have changed the 50ohm resistor, when I go back to stock rom I have baseband, I have both imei, but I have no signal, if I want to call a message appears saying "deactivate the airplane mode to call"
Click to expand...
Click to collapse
Its because of qcn you used its not compatible with your device.
dashti.95 said:
Its because of qcn you used its not compatible with your device.
Click to expand...
Click to collapse
I used the published QCN ENG and edited it with the imei that I found in the original box of the equipment, now both imei appear in the global Rom but I have the ghost plane mode, absolutely everything works except the mobile radio
felixpaz1992 said:
I have followed the guide, I was able to recover the original imei that came in the box, I have changed the 50ohm resistor, when I go back to stock rom I have baseband, I have both imei, but I have no signal, if I want to call a message appears saying "deactivate the airplane mode to call"
Click to expand...
Click to collapse
two questions:
1.Which NON-HLOS you used?Stock or Eng?
2.What type of Qcn you used?.xqcn or .qcn?