Develop Bugs

[6039] - ***GUIDE*** - How to return the fastboot commands on already upgraded device

Your warranty is void. I'm not responsible if your device is hard bricked by using the procedure below. The method described below has been tested on 6039Y, 6039S, 6039H (with the archives for 6039Y) and 6039K (with the 6039S archive) and is confirmed that it works.
What to expect on successful completion:
- you will have access to the fastboot commands (removed by the latest upgrade).
- you should be able to check for OTA updates and to download them, but you will not be able to install them.
What's needed:
-------------------
1. I hate when I must say this ... but ... a Windows PC.
2. QPST version 2.7.422 (you can find it on the net as 2.7 build 422). This is a link to one such version (found through Google). If there are problems with this link please let me know. I will try to find another one (you can do it yourself too).
3. Drivers in order the device to be recognized when is in Download mode. Install Mobile Upgrade Q 4.8.7 the necessary drivers are installed with it. It can be downloaded from here.
4. The files from the archives below. Please use the archive which is especially for your device ... in theory if you use the archive for different device (e.g. the archive for 6039S on 6039Y (with the standard partitions)) you should have a repartitioned device at the end, and only the resize2fs command should be enough to start to utilize the whole memory chip ... but you will loose the possibility to sweat a little bit when do the repartitioning by following the guide for it .
- 6039Y (8GB stock partition sizes) (md5sum: 860789bedb63da5c5976c24825c29d47)
- 6039Y (repartitioned by following the repartitioning guide) (md5sum: c2f8ff3cfc683e46fbf5d797103de71b)
- 6039S (md5sum: dfd04067230b5709729c70cac61ffd52)
How to proceed:
--------------------
1. Install all the necessary software.
2. Unpack the downloaded archive for your device.
3. Power off the device. Connect it with the USB cable to the PC. Wait the battery symbol to disappear and hold both volume keys and the power button. You should see a red screen with a warning sign and a scheme. Then hold the volume up button. The display will stay lit but nothing will be shown on it from now on until the end of the procedure.
4. When the device is in Download mode under the windows device manager -> Ports (COM & LPT) you should see Android HS-USB QDLoader 9008 (COMXX)
5. Open the windows explorer and find the installation folder of QPST (mine is under Program Files (x86)\Qualcomm\QPST). From the bin sub-directory start QFIL as administrator.
6. In QFIL the COM port number as seen under the windows device manager should be selected automatically.
7. The rest must be done from QFIL:
- Programmer path: _____ - Click on the Browse button against it and from the extracted archive select prog_emmc_firehose_8916.mbn
- Search Path: _____ - if the path is not selected automatically after the programmer selection click on the Browse button against it and select the folder where the archive has been extracted.
- Load XML - click on it and first select rawprogram0.xml from the archive, then the patch0.xml file.
- Click on the Download button. The process should finish quickly (few seconds ... up to a minute). If everything is OK the phone will be restarted automatically and the fastboot commands will be available again.
(If you feel unsure to proceed or not but your device is already in download mode ... disconnect the USB cable and hold both volume keys and the power button to restart it).
Screenshots from QFIL is possible to be provided later ...

Reserved....

Alright I guess I'll be the guinea pig here.... Few questions beforehand:
I currently have the 6039Y version without having repartitioned... Using the repartitionned one would directly give me a repartitionned memory? Did I understand that correctly?
Did I dream about you saying that you might have a way to fix hard bricks? Because I might very well brick mine with my usual luck
About the updates... If there were any later OTA updates (I know it's unlikely) would there be a way to apply them still?

Rorshan said:
Alright I guess I'll be the guinea pig here.... Few questions beforehand:
I currently have the 6039Y version without having repartitioned... Using the repartitionned one would directly give me a repartitionned memory? Did I understand that correctly?
Did I dream about you saying that you might have a way to fix hard bricks? Because I might very well brick mine with my usual luck
Click to expand...
Click to collapse
In theory yes, but is untested. Yes, hard bricks should be fixable with these tools and with slightly different files. But as this requires a full copy of the memory chip and for the moment I have such copy only from my device, I can recover only my device (or others which will become the same as mine ... this means radio, languages, apps etc. ).
About the updates... If there were any later OTA updates (I know it's unlikely) would there be a way to apply them still?
Click to expand...
Click to collapse
Yes, but modified
Edit: What do I do here? I guess a missing font file shouldn't bother me, but still I'd like some advice here
Click to expand...
Click to collapse
No idea ... try with ignore. I didn't have have any problems with mobile upgrade q.

petrov.0 said:
In theory yes, but is untested. Yes, hard bricks should be fixable with these tools and with slightly different files. But as this requires a full copy of the memory chip and for the moment I have such copy only from my device, I can recover only my device (or others which will become the same as mine ... this means radio, languages, apps etc. ).
Yes, but modified
No idea ... try with ignore. I didn't have have any problems with mobile upgrade q.
Click to expand...
Click to collapse
Untested doesn't sound nice... I guess I'll go with the normal way and worry about the repartition afterwards.
I cancelled the install and reinstalled with no issue
I guess this is it. Either way I'll come here to cry, be it from joy or sadness/anger
---------- Post added at 07:46 PM ---------- Previous post was at 07:26 PM ----------
Well I'm done and my phone resetted just fine... I freaked for a minute when it took a bit longer than usual for my phone to pick up signal.
And......
fastboot -i 0x1bbb devices
48fee072 fastboot
Click to expand...
Click to collapse
I haven't tried TWRP yet since I don't really know what version I should be using... Any idea @petrov.0 ?

Rorshan said:
Untested doesn't sound nice... I guess I'll go with the normal way and worry about the repartition afterwards.
I cancelled the install and reinstalled with no issue
I guess this is it. Either way I'll come here to cry, be it from joy or sadness/anger
---------- Post added at 07:46 PM ---------- Previous post was at 07:26 PM ----------
Well I'm done and my phone resetted just fine... I freaked for a minute when it took a bit longer than usual for my phone to pick up signal.
And......
I haven't tried TWRP yet since I don't really know what version I should be using... Any idea @petrov.0 ?
Click to expand...
Click to collapse
For normal use (flashing) the latest from 12.09.2015. For the repartitioning boot with the one from the repartitioning thread.

Thanks! I will try it now!
EDIT:
It all works

petrov.0 said:
For normal use (flashing) the latest from 12.09.2015. For the repartitioning boot with the one from the repartitioning thread.
Click to expand...
Click to collapse
Alright TWRP seems to work fine, I'm doing backups at the moment. Thank you so much! You're such a lifesaver. Quick last question... I think I'm going to root and repartition. Does it matter at all which I do first?

Rorshan said:
Alright TWRP seems to work fine, I'm doing backups at the moment. Thank you so much! You're such a lifesaver. Quick last question... I think I'm going to root and repartition. Does it matter at all which I do first?
Click to expand...
Click to collapse
This question is for the other thread ... but no, it doesn't matter.

Do you feel its safe to test this on 6039s?

xStealth said:
Do you feel its safe to test this on 6039s?
Click to expand...
Click to collapse
Well good question. The files for the S have been generated only on the base of the partition numbers (not their names) and their sizes ... they look the same as those on the Y but ... I think it's safe.

xStealth said:
Do you feel its safe to test this on 6039s?
Click to expand...
Click to collapse
Can further confirm that this worked on my 6039S. No bricking, and fastboot works as promised!
A BIG thanks petrov.0!

Bradlee22 said:
Can further confirm that this worked on my 6039S. No bricking, and fastboot works as promised!
A BIG thanks petrov.0!
Click to expand...
Click to collapse
He already did this. Read the first line from the first post.

petrov.0 said:
He already did this. Read the first line from the first post.
Click to expand...
Click to collapse
Oh, right on. I wasn't sure who had confirmed it at that point. Thanks again for all your work on this!

Update
The link and the md5sum in the first post for the repartitioned 6039Y have been updated as one of the files was missing from the archive. Thanks @kkkk2222 for finding the error.

Worked a treat, fantastic work folks.
http://www.modaco.com/news/android/you-can-turn-your-8gb-idol-3-47-into-a-16gb-really-r1521/
Used Parallels on a Mac, no problem!
P

@petrov.0
For those who end up stuck in bootloops(on both 6039's and 6045's) with factory recovery is there a way this method could be used to either 1) flash twrp to the device or 2) force the device into bootloader?
If a user can get to bootloader (and has fastboot) then they could attempt to fix their own issue.

famewolf said:
@petrov.0
For those who end up stuck in bootloops(on both 6039's and 6045's) with factory recovery is there a way this method could be used to either 1) flash twrp to the device or 2) force the device into bootloader?
If a user can get to bootloader (and has fastboot) then they could attempt to fix their own issue.
Click to expand...
Click to collapse
1. Yes, it should be possible by using the same tools with different files. But if they flash their system image backup this will lead to a big mess ... they will have a partially upgraded device. Probably if they use the fix permissions option or force the reinstall of SuperSU from the recovery this will be the end of the bootloops (these are unconfirmed speculations though). I need the gpt table from the device (6045) to generate the necessary files.
Code:
dd if=/dev/mmcblk0 of=<path to the sd_card>/gpt.bin bs=512 count=34
2. No.

petrov.0, first of all - thx for your great work. I have a theoretical question about QFIL and partition flashing. Is it necessary to flash all of this partitions in rawprogram0.xml:
sbl1.mbn
rpm.mbn
tz.mbn
hyp.mbn
aboot.mbn
gpt_main0.bin
gpt_backup0.bin
For working fastboot we need only aboot (emmc_appsboot) from previous firmware version (or i'm wrong?), if we short rawprogram0.xml only for aboot and gpt, like this:
Code:
<?xml version="1.0" ?>
<data>
<!--NOTE: This is an ** Autogenerated file **-->
<!--NOTE: Sector size is 512bytes-->
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="aboot.mbn" label="aboot" num_partition_sectors="2048" physical_partition_number="0" size_in_KB="1024.0" sparse="false" start_byte_hex="0xc18c000" start_sector="396384"/>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="aboot.mbn" label="abootbak" num_partition_sectors="2048" physical_partition_number="0" size_in_KB="1024.0" sparse="false" start_byte_hex="0xc28c000" start_sector="398432"/>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="gpt_main0.bin" label="PrimaryGPT" num_partition_sectors="34" physical_partition_number="0" size_in_KB="17.0" sparse="false" start_byte_hex="0x0" start_sector="0"/>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="gpt_backup0.bin" label="BackupGPT" num_partition_sectors="33" physical_partition_number="0" size_in_KB="16.5" sparse="false" start_byte_hex="(512*NUM_DISK_SECTORS)-16896." start_sector="NUM_DISK_SECTORS-33."/>
</data>
Phone doesn't brick after flashing?
p.s. And another one question. Do you know where the testpoint on 6039Y located? After several my experiments (not with your files, i was bricked it by myself i have bricked phone. There is no download mode (9008 com port not appears in my case), only turned on LED on front panel. Any actions with holding both volume buttons and power button doesn't get success, i think in this case testpoint will help. But i don't know where is it. If somebody need - i can attach photo of PCB.

petrov.0 said:
1. Yes, it should be possible by using the same tools with different files. But if they flash their system image backup this will lead to a big mess ... they will have a partially upgraded device. Probably if they use the fix permissions option or force the reinstall of SuperSU from the recovery this will be the end of the bootloops (these are unconfirmed speculations though). I need the gpt table from the device (6045) to generate the necessary files.
Code:
dd if=/dev/mmcblk0 of=<path to the sd_card>/gpt.bin bs=512 count=34
2. No.
Click to expand...
Click to collapse
Code:
/mmcblk0 of=/storage/sdcard1/gpt.bin bs=512 count=34 <
dd: /dev/mmcblk0: No such file or directory
Now a cat of /proc/partitions shows 179 0 15267840 mmcblk0 so I have no idea why it says it's not found. [I can confirm none of the mmc* are under /dev. I have a find running to see where it says it is.....ok..for us it's in /dev/block/mmcblk0 ]
Just drop .zip off the end of the name..it's not actually zipped but couldn't upload a .bin.

Redmi 3S bootloader CRACKING method

Maybe we all faced xiaomi bootloader unlocking problems sometimes.We tried many ways to unlock it but failed. Or maybe we have a second-hand Redmi 3S with account locked.Then,there is a brand new way to unlock it.
If you can unlock your phone ,DONT try this method
Instead of using miflashunlock tool,we'll try to crack the aboot (emmc_appsboot.mbn) partition on our phone. But we don't have permission to write any system partition without unlocking.So we need to get the permission first.
The easiest way to get it is to boot your phone into Qualcomm 9008 EDL mode.This mode is integrated into the SoC so we always will be able to enter it.BUT Xiaomi has taken some actions to block it:crying:.So we do need to have a try.
The first and easiest way to enter 9008 is to reboot your phone into fastboot ,then type 'fastboot oem edl'. If this way doesn't work ,try the second way.
Second way:A 'Xiaomi Deep Flash Cable' is needed.You could buy it or diy it.(If you want to diy,just cut open a microusb cable,the you see four wires.Cut open the green one and the black one .Then screw together the four copper wire.)
Fully shut your phone down and use the cable to connect phone&PC.Nothing seemed to happen,but now your phone is under 9008. Then use a normal cable to connect.You will hear the computer installing a new device.
Third way: (Not recommended) Open the back of the phone ,tear the shell on the main circuit board down.Then you will see two copper points . Use a wire or tweezer to connect them. Then hold on,use your second hand to connect a USB cable(normal,not deep flash cable).
After booting into 9008 mode,you need to install the drivers of 9008 . Install this miflash .
https://drive.google.com/uc?id=0Byw7MVzb0VBXUnhFcmZmdWFaQkU&export=download
Open miflash and you will see a com port (it's your device).If not check device manager .Install the drivers properly.
Then, everything is ready.
Download and extract the package below.
https://drive.google.com/uc?id=0Byw7MVzb0VBXZUctUFYzb1BrSGM&export=download
An 'unlock' folder will be created and the unlocked version of bootloader is placed in. Then choose the folder in miflash. Click the flash button.It will be done in a few seconds.After it displayed 'Success',hold phone's power button for 15sec until it reboot. Maybe your device will stuck at logo.But don't worry. Just hold power and volume- together for 15sec until it enters fastboot.
Then the most amazing thing will happen!
Type 'fastboot oem unlock' on the computer .
Then you will see a UNLOCKING warning on the phone screen,it looks like Nexus's.Use your volume key and choose Yes. Phone reboots, stuck at logo again. But now everything is done. Just re enter fastboot and flash a custom recovery.
(Because the unlocking will wipe data using recovery, I have made an action in the 9008 flash package to erase the recovery partition to prevent losing data.)
After all, your phone has fully unlocked.So doing anything is easy.
BUT one con.You can't upgrade bootloader. But any firmware partition update will update it. So when you are flashing any zip file,you need to delete firmware-update/emmc_appsboot.mbn in the zip first. You can't use MIUI OTA.

Before 9008 Driver installation read this: https://www.top-password.com/blog/how-to-disable-driver-signature-enforcement-in-windows-10-8-7/
Without this setting, the driver can not be installed.
Use an 64bit Win 7 or 10 for Miflash.

Such a long process. It took just one click to unlock BL using official method

fastboot oem edl
command just working with MIUI v7 stable, if you come with MIUI v8. It'll not work

Can I use it for all xiaomi phones or is it only for redmi 3s

Aamirsingh said:
Can I use it for all xiaomi phones or is it only for redmi 3s
Click to expand...
Click to collapse
Land only.

sunny54_8 said:
Such a long process. It took just one click to unlock BL using official method
Click to expand...
Click to collapse
but it is causing problem at 99% it shows that my device is not bound to mi account
but ive done it in developer option still it is not unlocking

I also had faced this problem but after knowing that I had two accounts So I tried with other one and it worked

Sounds too simple but I want to know if it really works I mean if anyone has tried it or not

Aamirsingh said:
Sounds too simple but I want to know if it really works I mean if anyone has tried it or not
Click to expand...
Click to collapse
Of course .I unlocked my phone in this way.

fxsheep said:
Of course .I unlocked my phone in this way.
Click to expand...
Click to collapse
Then I am probably going to unlock my Redmi 3s prime this way and I will also try to post this video on YouTube
---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------
Aamirsingh said:
Sounds too simple but I want to know if it really works I mean if anyone has tried it or not
Click to expand...
Click to collapse
Hey thanks for quick response

Anyone else tried this ?
---------- Post added at 18:03 ---------- Previous post was at 17:56 ----------
Install the drivers properly.
What drivers are required ? If computer does not automatically install them.
---------- Post added at 18:03 ---------- Previous post was at 18:03 ----------
Install the drivers properly.
What drivers are required ? If computer does not automatically install them.

Worked perfectly. Thanks

I can confirm it worked perfectly. There is one referenced file missing but I made it work by doing these changes:
remove all <program lines except ones mentioning aboot and aboot_bak from rawprogram0.xml
remove all <patch tags from patch0.xml
So it's fine to just program aboot and aboot_bak (bootloader). No other programming/patching seem to be necessary.

kex1xik said:
I can confirm it worked perfectly. There is one referenced file missing but I made it work by doing these changes:
remove all <program lines except ones mentioning aboot and aboot_bak from rawprogram0.xml
remove all <patch tags from patch0.xml
So it's fine to just program aboot and aboot_bak (bootloader). No other programming/patching seem to be necessary.
Click to expand...
Click to collapse
Basically need to remove those tags only?
---------- Post added at 01:14 PM ---------- Previous post was at 12:24 PM ----------
hiimpig1 said:
fastboot oem edl
command just working with MIUI v7 stable, if you come with MIUI v8. It'll not work
Click to expand...
Click to collapse
What does this means?
---------- Post added at 01:15 PM ---------- Previous post was at 01:14 PM ----------
babaarpit said:
Worked perfectly. Thanks
Click to expand...
Click to collapse
What did i do when u successful flashed the files ?

Exactly. I modified it this way:
rawprogram0.xml:
Code:
<?xml version="1.0" ?>
<data>
<!--NOTE: This is an ** Autogenerated file **-->
<!--NOTE: Sector size is 512bytes-->
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="emmc_appsboot.mbn" label="aboot" num_partition_sectors="2048" physical_partition_number="0" size_in_KB="1024.0" sparse="false" start_byte_hex="0x18000000" start_sector="786432"/>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="emmc_appsboot.mbn" label="abootbak" num_partition_sectors="2048" physical_partition_number="0" size_in_KB="1024.0" sparse="false" start_byte_hex="0x18100000" start_sector="788480"/>
</data>
patch0.xml:
Code:
<?xml version="1.0" ?>
<patches>
</patches>
and flashed the folder using MiFlash.exe with phone in EDL mode. I was able to enter edl mode by just doing "fastboot oem edl" from standard fastboot xiaomi screen.
Maybe patch0.xml can be deleted completely, I don't know but I kept it.
After flashing this aboot and booting into fastboot again, I was able to do "fastboot oem unlock-go" to unlock the bootloader without waiting for Xiaomi to give me approval or bothering with their stupid one unlock per 3 day policy (error "After 72 hours of trying to unlock the device").
I did this successfully on a new Xiaomi 3s Prime 3GB I bought from eBay.

What did i do when u successful flashed the files ?
Click to expand...
Click to collapse
I didnt use these files. I researched some more and used files from Here (XiaomiFirmware dot com)
The method is more or less the same just the files are different
First step involved mi flash tool using these files :
dummy.img
emmc_appsboot.mbn
patch0.xml
prog_emmc_firehose_8937_ddr.mbn
rawprogram0.xml
All these are diff from ones linked in OP
Update : I checked and the two xml files are same as you modified
Code:
<?xml version="1.0" ?>
<data>
<!--NOTE: This is an ** Autogenerated file **-->
<!--NOTE: Sector size is 512bytes-->
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="emmc_appsboot.mbn" label="aboot" num_partition_sectors="2048" physical_partition_number="0" size_in_KB="1024.0" sparse="false" start_byte_hex="0x18000000" start_sector="786432"/>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="emmc_appsboot.mbn" label="abootbak" num_partition_sectors="2048" physical_partition_number="0" size_in_KB="1024.0" sparse="false" start_byte_hex="0x18100000" start_sector="788480"/>
</data>
**and**
<?xml version="1.0" ?>
<patches>
</patches
Next step required modified adb, fastboot i think
Code:
fastboot.exe devices
fastboot.exe oem unlock-go
then
Code:
fastboot.exe devices
fastboot.exe flash recovery recovery.img
fastboot.exe boot recovery.img
I replaced their image file with TWRP latest

Always got the error during flashing "hello packet not....." Any solution

Aamirsingh said:
Always got the error during flashing "hello packet not....." Any solution
Click to expand...
Click to collapse
Make sure your device is redmi 3s/x

fxsheep said:
Make sure your device is redmi 3s/x
Click to expand...
Click to collapse
Successful

Need "persist" Partition

Hi there,
I need your help. My Persist Partition is damaged and I have no Backup. Cann anyone send me this one?
Found only this (For OnePlus 5) but the way is the same:
adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
exit
Click to expand...
Click to collapse
Please help me... :crying::fingers-crossed:

I'm Stuck aswell
Can anyone please lend their persist partition zip file. even I have all my sensors corrupt.

Here you go hope that works fine

The Unbrick tools also include the persist image. Why not just use them to revert your phone to a factory-like state? Just a few clicks away.

That doesnt work.
morphvale said:
The Unbrick tools also include the persist image. Why not just use them to revert your phone to a factory-like state? Just a few clicks away.
Click to expand...
Click to collapse
Tried it a lot of times. that doesnt work. plus i just noticed that the image uploaded is 32mb in size while the one in full unbrick tool is 4mb.
---------- Post added at 03:46 PM ---------- Previous post was at 02:58 PM ----------
liam_davenport said:
Here you go hope that works fine
Click to expand...
Click to collapse
Appreciate the help but when I flash the partitions, phone just doesnt boot up at all like it does with the broken partition. Seems like some other software malfunction.
Do you mind telling what oxygen os you are using?

No video recording after rollback from Pie to Oreo

Short video still works but normal video does nothing. Other apps like OpenCamera and Whatsapp return error after trying to record video...
Anyone can help?

Same problem here. May be a Bug in V9.6.11.0.0 only ?

Rdeniro67 said:
Same problem here. May be a Bug in V9.6.11.0.0 only ?
Click to expand...
Click to collapse
No i have 9.6.10.0.0
It's because of that xiaomi was saying that rollback to Oreo is not recommended because of pie makes big changes to the system
Or because of the modem.img we have installed from pie

AnonymousAL said:
No i have 9.6.10.0.0
It's because of that xiaomi was saying that rollback to Oreo is not recommended because of pie makes big changes to the system
Or because of the modem.img we have installed from pie
Click to expand...
Click to collapse
is it true, is there a method for this

1. Download latest Stable rom Oreo
2 Unzip and go in to image folder
3. Open file rawprogram0.xml on notepad
4. Find the command line :
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xbfff400" start_sector="393210"/>
5. in that line just add hi-lighted part (persist.img) or just copy and paste this line:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="persist.img" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xbfff400" start_sector="393210"/>
6. put your device on EDL mode, use minimal adb with command (fastboot oem edl)
7. Flash with MiFlash
8. Reboot
This method does not cause a blank signal/simcard 2 not registered, and the video camera runs normally. and this method does not fix swap simcard.

WARNING
ROM V9.6.11.0.0 is corrupt. Install a previous one and then update

knotdead said:
1. Download latest Stable rom Oreo
2 Unzip and go in to image folder
3. Open file rawprogram0.xml on notepad
4. Find the command line :
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xbfff400" start_sector="393210"/>
5. in that line just add hi-lighted part (persist.img) or just copy and paste this line:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="persist.img" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xbfff400" start_sector="393210"/>
6. put your device on EDL mode, use minimal adb with command (fastboot oem edl)
7. Flash with MiFlash
8. Reboot
This method does not cause a blank signal/simcard 2 not registered, and the video camera runs normally. and this method does not fix swap simcard.
Click to expand...
Click to collapse
Does this method need unlocked bootloader? Also, are we supposed to put back the file in the ROM and flash the full ROM? Is there a way to just flash this single file?

agamotto said:
Does this method need unlocked bootloader? Also, are we supposed to put back the file in the ROM and flash the full ROM? Is there a way to just flash this single file?
Click to expand...
Click to collapse
yes it need unlock the bootloader.

Going back from pie, you can do easily by flashing 9.6.4.0 stock via EDL... That's it! No video problem, no swapped sims... And ota brings you in one step back to 9.6.11.0!

knotdead said:
1. Download latest Stable rom Oreo
2 Unzip and go in to image folder
3. Open file rawprogram0.xml on notepad
4. Find the command line :
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xbfff400" start_sector="393210"/>
5. in that line just add hi-lighted part (persist.img) or just copy and paste this line:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="persist.img" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xbfff400" start_sector="393210"/>
6. put your device on EDL mode, use minimal adb with command (fastboot oem edl)
7. Flash with MiFlash
8. Reboot
This method does not cause a blank signal/simcard 2 not registered, and the video camera runs normally. and this method does not fix swap simcard.
Click to expand...
Click to collapse
Voodoojonny said:
Going back from pie, you can do easily by flashing 9.6.4.0 stock via EDL... That's it! No video problem, no swapped sims... And ota brings you in one step back to 9.6.11.0!
Click to expand...
Click to collapse
try both, doesn't work at all

adhitore said:
try both, doesn't work at all
Click to expand...
Click to collapse
Ok, my full way was (originally I tried to get volte running on havoc)
- Flashed havoc over pie and installed ims and imssettings in all combinations to system/app and system/priv-app -> here I got the first time the sim switch and an empty signal sim (btw: switching to 3g gives you back the signal)
- realized I will not get it running, so i flashed 9.6.11.0 via edl: problem still persistant
- flashed 9.6.11.0 again via fastboot: same
- flashed 9.6.4.0 via edl: everything fine!
I just started realizing that I messed up my ril... Lucky again! And just checked: video recording via snap and gcam works without problems! Can´t check miui-cam, couse I´m on Havoc...

agamotto said:
Does this method need unlocked bootloader? Also, are we supposed to put back the file in the ROM and flash the full ROM? Is there a way to just flash this single file?
Click to expand...
Click to collapse
adhitore said:
try both, doesn't work at all
Click to expand...
Click to collapse
im tested in 9.6.10.0 and work
---------- Post added at 05:12 PM ---------- Previous post was at 05:08 PM ----------
Voodoojonny said:
Going back from pie, you can do easily by flashing 9.6.4.0 stock via EDL... That's it! No video problem, no swapped sims... And ota brings you in one step back to 9.6.11.0!
Click to expand...
Click to collapse
I got a simcard 2 not registered bug and a swap sim after a downgrade at 9.6.4.0

knotdead said:
im tested in 9.6.10.0 and work
---------- Post added at 05:12 PM ---------- Previous post was at 05:08 PM ----------
I got a simcard 2 not registered bug and a swap sim after a downgrade at 9.6.4.0
Click to expand...
Click to collapse
lucky you,but it doesn't work for me

Nothing of these fixes which are mentioned in this thread worked for me, but I found another solution!
This guide works perfectly for me!
https://forum.xda-developers.com/showpost.php?p=78496783&postcount=40
I don't get the "sim-card is not registered" -bug and videorecording works also! But I don't know if you can use two sim-cards

I was facing that problem before i downgraded.
I flashed pixel experience and returned to 9.6.4.0 and updated to 9.6.11.0 and problem was gone
I dont know how i fixed

Kineceleran said:
I was facing that problem before i downgraded.
I flashed pixel experience and returned to 9.6.4.0 and updated to 9.6.11.0 and problem was gone
I dont know how i fixed
Click to expand...
Click to collapse
you saved my life! <3

NeoZX58 said:
you saved my life! <3
Click to expand...
Click to collapse

I just want to give a easy solution to fix all problem during the downgrade from pie to oreo
I tried all suggestion but edl mode. I found that if you download the first firmware daisy 9.6.4.0, then download the firmware daisy_global_images_V10.0.2.0.PDLMIFJ_9.0 extract the modem.img and copy into the folder of daisy 9.6.4.0 you just fix the sim cards problem. Now you can flash using miflash. After that first boot up the only problem is that the camera wont record the video..... so now just update the firmware version to the latest Oreo 9.6.11.0 , When the process ends the phone works completely.

********

r4nm4 said:
Hi, I had the same issue. After debug basically I found out that the Audio Codec was broken (short video use poor codec, thats why it works).
After many search and post, no one helped me.
The only way I found to fix it was install again Oreo from flash. Factory reset didn't fix.
Let me know if you find other way or some one else will answer you.
If you want to investigate about that, remember that is regarding Audio Codec.
Click to expand...
Click to collapse
Thanks but I've since upgraded to Pie and issue is gone.

Question How do I make a full system backup?

How do I make a full system backup including the currently installed firmware version? I would like to do this before I root the device. I have Global C61 and can’t find a full installer for reinstall of anything newer than C48. Thanks

I'm interested in this also....in addition, if you are on A11 with TWRP, when backing up do you select all partitions?

My choice (if you have the space) is to use EDL (or ROM bootloader on other devices) to do a complete save of your flash (as one file).
Ok, you might want to save all the partitions individually too, that will allow you to do rollbacks but keep the current userdata.
In the final analysis you can't do too much backing up (if you have the space).

TheGhost1951 said:
if you are on A11
Click to expand...
Click to collapse
I have A12, C61
Renate said:
use EDL
Click to expand...
Click to collapse
How do I do this?
Renate said:
save all the partitions individually
Click to expand...
Click to collapse
How do I do this?
Renate said:
if you have the space
Click to expand...
Click to collapse
You mean on my computer or on the phone? I have plenty of space in both locations, though

Just use Oneplus clone phone

I meant space on your desktop, flash drives, SD cards.
I'm not familiar with any specific OnePlus tools.
I just meant this as general advice for any device where you can get R/W access to the flash without actively using any of it at all.
That means EDL for Qualcomm devices, MTKClient for MediaTek devices, FEL mode for Allwinner devices...

DroidShift79 said:
Just use Oneplus clone phone
Click to expand...
Click to collapse
That's not what he wants. He's talking about NAND backup.

DroidShift79 said:
Just use Oneplus clone phone
Click to expand...
Click to collapse
Doesn't backup app data....

I can backup all partitions with MSM tool, just need fastboot script to "flash all" so that it doesn't have to be one img at a time.

Oh yeah, I got it wrong, sry.
SwiftBackup or titanium backup could help with apps and app data.
And if that's still not enough I would consider EDL/ MSM Tool

TheGhost1951 said:
I can backup all partitions with MSM tool, just need fastboot script to "flash all" so that it doesn't have to be one img at a time.
Click to expand...
Click to collapse
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
That could lead you in the right direction.

Saving the entire flash is the simplest, most bombproof and yes, least versatile way.
Of course you can save partitions individually also.
It's not even rocket science to make a script out of a partition listing.
You can also restore just fine with EDL, you don't particularly need fastboot.
Edit: See, I just backed up 32GB on my device:
Code:
C:\>edl /r /c61071327 nul:
Found EDL 9008
Configuring... Nope, configuring... Ok
Requesting read ... Ok, receiving 100% Ok
Now, where did that file go?

Renate said:
Saving the entire flash is the simplest, most bombproof and yes, least versatile way.
Of course you can save partitions individually also.
It's not even rocket science to make a script out of a partition listing.
You can also restore just fine with EDL, you don't particularly need fastboot.
Edit: See, I just backed up 32GB on my device:
Code:
C:\>edl /r /c61071327 nul:
Found EDL 9008
Configuring... Nope, configuring... Ok
Requesting read ... Ok, receiving 100% Ok
Now, where did that file go?
Click to expand...
Click to collapse
That's an approach i didn't know. Are you in the mood of writing a short step by step guide

The basics are getting into EDL mode and having your desktop EDL client.
The MSM tool is one client but as I've never used it, I'm not sure of its capabilities.
https://github.com/bkerler/edl is a Python imlementation.
Then there's my Windows implementation edl.exe that's in my sig.
On Windows I prefer using WinUSB directly instead of silly Qualcomm VCOM drivers.
Use https://zadig.akeo.ie/ and install WinUSB on 05c6/9008
You'll be needing a "loader" which is basically a replacement for SBL/XBL which does useful things.
A collection of loaders can be found here: https://github.com/bkerler/Loaders/
The correct one (if it exists) can be found automatically if you are using B. Kerler's client and you've downloaded everything.
If you're using my code the rest of this all deals with the specifics.
You can get the HWID and Hash and either manually look for a loader or ask me.
Code:
C:\>edl.exe /l
Found EDL 9008
Serial: 12345678
HWID: 000cc0e100000000, QC: 000cc0e1, OEM: 0000, Model: 0000
Hash: 7be49b72f9e43372-23ccb84d6eccca4e-61ce16e3602ac200-8cb18b75babe6d09
(That's a slash-ell up above.)
Then you look for something somewhere called 000cc0e100000000-7be49b72f9e43372
You download it and rename it something sane, like "phone.bin".
Code:
C:\>edl.exe /lphone.bin
...
Sending phone.bin 100% Ok
Waiting for Firehose... Ok
C:\>edl.exe /g
...
lots of partition listing
...
If that works, you have eMMC. If the /g part didn't work then you have UFS, in which case you can add /u to all commands: edl.exe /u /g
Look at the partition listing take the last partition and add the offset and count and you have the total number of sectors (either 512 eMMc or 4096 UFS).
Then just do the same command as up above.
Code:
C:\>edl.exe /r /c6107132 mybackup
You could also edl.exe /r /p1 partition1 or edl.exe /r /pboot boot.img.
And when you're done having fun edl.exe /z.

And if you have everything in one big 32, 64 or 128 GB chunk and you suddenly need to get a copy of the boot partition,
there are tools in Windows and Linux to chop that all up into partitions.

How do I properly exit EDL mode? I was stuck in it for a while, black screen no usb devices, but it eventually fixed itself.
Also I seem to be running into issues actually taking a backup: (Trying to back it up before trying lineage/crDroid, twrp fails to take an image as well)
Code:
K:\OnePlus9Pro>edl /l
Found EDL 9008
Serial: f709f1be
HWID: 001350e100514d67, QC: 001350e1, OEM: 0051, Model: 4d67
Hash: a26bc25799770106-f32c2856606a87ad-9c1e997d25b5e80f-f30b0e47e4c85e15
K:\OnePlus9Pro>edl /l9proloader.bin
Found EDL 9008
Resetting Sahara
Serial: f709f1be
HWID: 001350e100514d67, QC: 001350e1, OEM: 0051, Model: 4d67
Hash: a26bc25799770106-f32c2856606a87ad-9c1e997d25b5e80f-f30b0e47e4c85e15
Sending 9proloader.bin 100% Ok
Waiting for Firehose... Ok
K:\OnePlus9Pro>edl /g
Found EDL 9008
Configuring... Ok
Requesting GPT 0 header... Ok, receiving...
Could not read device
K:\OnePlus9Pro>edl /u /g
Could not find EDL device
K:\OnePlus9Pro>edl /l9proloader.bin
Could not find EDL device
K:\OnePlus9Pro>edl /l
Could not find EDL device
Next Session:
K:\OnePlus9Pro>edl /u /g
Found EDL 9008
Configuring... Ok
Requesting info...
<log value="ERROR: [ffu]FWversion:903." />
Ok
No LUNs found
K:\OnePlus9Pro>edl /r /u /l 9proloader.bin
Found EDL 9008
Resetting Sahara
Unknown cmd 6d783f3c in packet
K:\OnePlus9Pro>edl /g
Found EDL 9008
<log value="ERROR: Failed to run the last command -1" />
Configuring... Ok
Requesting GPT 0 header... No response

ajolly said:
How do I properly exit EDL mode? I was stuck in it for a while, black screen no usb devices, but it eventually fixed itself.
Also I seem to be running into issues actually taking a backup: (Trying to back it up before trying lineage/crDroid, twrp fails to take an image as well)
Code:
K:\OnePlus9Pro>edl /l
Found EDL 9008
Serial: f709f1be
HWID: 001350e100514d67, QC: 001350e1, OEM: 0051, Model: 4d67
Hash: a26bc25799770106-f32c2856606a87ad-9c1e997d25b5e80f-f30b0e47e4c85e15
K:\OnePlus9Pro>edl /l9proloader.bin
Found EDL 9008
Resetting Sahara
Serial: f709f1be
HWID: 001350e100514d67, QC: 001350e1, OEM: 0051, Model: 4d67
Hash: a26bc25799770106-f32c2856606a87ad-9c1e997d25b5e80f-f30b0e47e4c85e15
Sending 9proloader.bin 100% Ok
Waiting for Firehose... Ok
K:\OnePlus9Pro>edl /g
Found EDL 9008
Configuring... Ok
Requesting GPT 0 header... Ok, receiving...
Could not read device
K:\OnePlus9Pro>edl /u /g
Could not find EDL device
K:\OnePlus9Pro>edl /l9proloader.bin
Could not find EDL device
K:\OnePlus9Pro>edl /l
Could not find EDL device
Next Session:
K:\OnePlus9Pro>edl /u /g
Found EDL 9008
Configuring... Ok
Requesting info...
<log value="ERROR: [ffu]FWversion:903." />
Ok
No LUNs found
K:\OnePlus9Pro>edl /r /u /l 9proloader.bin
Found EDL 9008
Resetting Sahara
Unknown cmd 6d783f3c in packet
K:\OnePlus9Pro>edl /g
Found EDL 9008
<log value="ERROR: Failed to run the last command -1" />
Configuring... Ok
Requesting GPT 0 header... No response
Click to expand...
Click to collapse
I have yet to get twrp restore from backup to work properly. I just had to MSM my phone back to stock and start over from scratch cause TWRP restore messed things up....

TheGhost1951 said:
I have yet to get twrp restore from backup to work properly. I just had to MSM my phone back to stock and start over from scratch cause TWRP restore messed things up....
Click to expand...
Click to collapse
I've had success with older android versions, but not with 12. Annoyed that OnePlus updated the OS on me without warning, I thought I was just installing the latest security updates.
Just hoping to make a proper backup before flashing a new rom.

tk_xda said:
How do I make a full system backup including the currently installed firmware version? I would like to do this before I root the device. I have Global C61 and can’t find a full installer for reinstall of anything newer than C48. Thanks
Click to expand...
Click to collapse
Idk if this is what you're looking for but I love swiftbackup you can download it on the app store for free and move the file to your computer once it's complete or if you pay the fee you can back it up to whatever cloud storage you have it's only like 5 bucks for lifetime I believe, if you have root it'll also back up your app data so it restores all your apps as if you've just signed into them, they did put a warning recently of Google authenticator but mine still restored from a previous version

Renate said:
I meant space on your desktop, flash drives, SD cards.
I'm not familiar with any specific OnePlus tools.
I just meant this as general advice for any device where you can get R/W access to the flash without actively using any of it at all.
That means EDL for Qualcomm devices, MTKClient for MediaTek devices, FEL mode for Allwinner devices...
Click to expand...
Click to collapse
Hello dear i want to know
Are you in window 10? I mean which edl script you used is this in win10?
And is is there anyway to get rw in os12? In os11 its easy task
And about dump i try unpack ops and flash via dump command its take time and in the end get error
And device also not booted
I use this commamd
Edl py w extract