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

How to downgrade to Oreo 8.1

Hello I am Bran New to Flashing, I've Looked around and have a vague clue how to do this.
From what I gathered I have to fast boot, then use the mi flash tool with the ota rom of the oero 8.1
Again I have no clue, is there a straight tutorial available?

this one
https://forum.xda-developers.com/showpost.php?p=78473747&postcount=34 (don't change persist lines! just information for you how to flashing)
and this
https://forum.xda-developers.com/showpost.php?p=78496783&postcount=40 (for simcards fix)

Thanks @eremitein, I'm looking to downgrade too. We have to make fastboot flashing unlock and fastboot flashing unlock_critical before that I suppose.
Edit this lines adding filename
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="dummy.img" label="apdp" num_partition_sectors="512" physical_partition_number="0" size_in_KB="256.0" sparse="false" start_byte_hex="0xff400" start_sector="2042"/>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="dummy.img" label="msadp" num_partition_sectors="512" physical_partition_number="0" size_in_KB="256.0" sparse="false" start_byte_hex="0x13f400" start_sector="2554"/>
(ANd that fix the sim and videocamera problem?)
then fastboot oem edl and flash with miflash?

Nidea180 said:
Thanks @eremitein, I'm looking to downgrade too. We have to make fastboot flashing unlock and fastboot flashing unlock_critical before that I suppose.
Edit this lines adding filename
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="dummy.img" label="apdp" num_partition_sectors="512" physical_partition_number="0" size_in_KB="256.0" sparse="false" start_byte_hex="0xff400" start_sector="2042"/>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="dummy.img" label="msadp" num_partition_sectors="512" physical_partition_number="0" size_in_KB="256.0" sparse="false" start_byte_hex="0x13f400" start_sector="2554"/>
(ANd that fix the sim and videocamera problem?)
then fastboot oem edl and flash with miflash?
Click to expand...
Click to collapse
NO! red is wrong, dont do that or may brick your phone!!!
look again at https://forum.xda-developers.com/showpost.php?p=78496783&postcount=40
and this fix only simcards, none videocamera

eremitein said:
NO! red is wrong, dont do that or may brick your phone!!!
look again at https://forum.xda-developers.com/showpost.php?p=78496783&postcount=40
and this fix only simcards, none videocamera
Click to expand...
Click to collapse
Oh sorry I saw the good line but copy the wrong one :silly:
You try this? I know only fix sim problem but your videocamera works good?
The other way (https://forum.xda-developers.com/showpost.php?p=78473747&postcount=34) changing persist line you don't recommend? Doesn't look like big problem got swap sim cards if everything works good.

Nidea180 said:
Oh sorry I saw the good line but copy the wrong one :silly:
You try this? I know only fix sim problem but your videocamera works good?
The other way (https://forum.xda-developers.com/showpost.php?p=78473747&postcount=34) changing persist line you don't recommend? Doesn't look like big problem got swap sim cards if everything works good.
Click to expand...
Click to collapse
video rec work, 1080 HD
i tried only modem fix (but another method for linux), it's work
with persist be careful, because system may be broke after fix. ask in original thread

So? Is it possible to downgrade using MiFlash to Oreo?

jimmyoh said:
So? Is it possible to downgrade using MiFlash to Oreo?
Click to expand...
Click to collapse
Yes. Assuming your bootloader is unlocked.

hossman said:
Yes. Assuming your bootloader is unlocked.
Click to expand...
Click to collapse
Ok I'll unlock the bootloader then.
Sent from my Mi A2 Lite using XDA Labs

jimmyoh said:
Ok I'll unlock the bootloader then.
Click to expand...
Click to collapse
Unlocking bootloader will wipe your device.
Suggest backup

I downgrade yesterday and looks like all works good but there are some bug on rom V9.6.11.0.ODLMIFF
https://imgur.com/a/mnGFadU
I cant' uninstall those apps.
Somebody try another previous rom?
If I install previous version and lock the bootloader can update via ota to V9.6.11.0.ODLMIFF or only let update to pie?

hossman said:
Unlocking bootloader will wipe your device.
Suggest backup
Click to expand...
Click to collapse
Do I have to apply those fixes described in posts above or just flashing Tru MiFlash is enough to get it working?

[GUIDE] Canadian H933 compatibility with H930 ROMs

This guide assumes your bootloader is already unlocked, if it isn't unlock your bootloader then come back here.
This guide cuts down several other guides by removing unnecessary steps, those guides, marked Relevant, will be linked and they should all be read before starting.
This will take 2-4 hours.
BACKUP ALL DATA BEFORE PROCEEDING
ALL DATA WILL BE LOST
Files needed:
US998 Nougat KDZ - US99810C_03_1216.kdz
H933 Oreo KDZ - H93320H_00_OPEN_CA_OP_1123.kdz
LGUP & LG USB Drivers
LGUP+V30DLL_PATCHED (5).zip
TWRP (select which type you want, guide will refer to either as 'twrp.img')
lg-rctd-disabler-1.0.zip & no-verity-opt-encrypt-6.0.zip & Magisk-v18.0.zip
For ADB I recommend this but if you need this guide you would already have it
Step 00
Unlock your bootloader then come back here
Step 0 - Prep
Install LG mobile drivers, LGUP and ADB if you haven't already
Patch LGUP by extracting the LGUP+V30DLL_PATCHED (5).zip into the LGUP install directory, overwriting the EXE and adding the folder structure for common DLLs
Step 1 - Restore H933
If you already have a DUMP from H933 firmware with working data, move to Step 3
Connect phone to patched LGUP
Select REFURBISH
Load H933 KDZ
Start
You should have mobile data again however no TWRP and no root
Step 2 - DUMP partitions
You may need to re-enable ADB Debugging before continuing
Close LGUP and disconnect phone
Reopen LGUP and reconnect phone
Select DUMP
Start, select all then select a folder for the files to be dumped to
This should take about an hour with all partitions selected. Only 9 are needed however, it may be useful in the future to have all of them.
The 9 that are needed are OP, modem, modemst1, modemst2, misc, persist, ftm, pstore, recovery.
Mine always ended in a timeout error however that seemed to not be a problem.
Remove "_COMX" and add ".bin" to the 9 files.
Now is a good time to copy these 9 files along with lg-rctd-disabler-1.0.zip, no-verity-opt-encrypt-6.0.zip and Magisk-v18.0.zip to your External SD if you have one, otherwise they can be pushed later.
Step 3 - PARTITION DL US998 (Relevant)
Close LGUP and disconnect phone and restart
Reopen LGUP and reconnect phone
Select PARTITION DL
Load US998 KDZ
Start, Select All, Yes to partition changes window
When its done it will attempt to boot and you'll get flashes of an image, perform Master Reset
Step 4 - Flash TWRP (Relevant)
Get through setup screens
Enable ADB
In Command Prompt ->
Code:
adb reboot bootloader
Once rebooted ->
Code:
fastboot flash recovery path/to/twrp.img
Once completed ->
Code:
fastboot boot twrp.img
Swipe to allow modifications
Wipe -> Format Data -> yes
Wipe -> Factory Reset
Reboot -> Recovery
Unplug the cable
Reboot -> Power Off
Step 5 - PARTITION DL H933 (Relevant)
Enter Download Mode (Hold Vol + and plug in cable)
Open LGUP
Select PARTITION DL
Load H933 KDZ
Start, Select All, UNSELECT Recovery, Yes to partition changes window
Your phone should reboot to TWRP when finished
Step 6 - Fix Partitions (Relevant)
Swipe to allow modifications
Wipe -> Format Data -> yes
Wipe -> Factory Reset
Reboot -> Recovery
If you copied Magisk-v18.0.zip, no-verity-opt-encrypt-6.0.zip and lg-rctd-disabler-1.0.zip to an External SD then flash them now, in that order
Otherwise
Code:
adb push path\to\Magisk-v18.0.zip /sdcard/
adb push path\to\no-verity-opt-encrypt-6.0.zip /sdcard/
adb push path\to\lg-rctd-disabler-1.0.zip /sdcard/
then flash them in that order
If you copied the 9 .bin files then Advanced -> File Manager
Copy each .bin to /sdcard/
Otherwise
Code:
adb push path\to\OP.bin /sdcard/
adb push path\to\modem.bin /sdcard/
adb push path\to\modemst1.bin /sdcard/
adb push path\to\modemst2.bin /sdcard/
adb push path\to\misc.bin /sdcard/
adb push path\to\persist.bin /sdcard/
adb push path\to\ftm.bin /sdcard/
adb push path\to\recovery.bin /sdcard/
adb push path\to\pstore.bin /sdcard/
In Comamnd Prompt ->
Code:
adb shell
dd if=/sdcard/OP.bin of=/dev/block/bootdevice/by-name/OP
dd if=/sdcard/modem.bin of=/dev/block/bootdevice/by-name/modem
dd if=/sdcard/modemst1.bin of=/dev/block/bootdevice/by-name/modemst1
dd if=/sdcard/modemst2.bin of=/dev/block/bootdevice/by-name/modemst2
dd if=/sdcard/misc.bin of=/dev/block/bootdevice/by-name/misc
dd if=/sdcard/persist.bin of=/dev/block/bootdevice/by-name/persist
dd if=/sdcard/ftm.bin of=/dev/block/bootdevice/by-name/ftm
dd if=/sdcard/pstore.bin of=/dev/block/bootdevice/by-name/pstore
dd if=/sdcard/recovery.bin of=/dev/block/bootdevice/by-name/recovery
Unplug phone
Reboot -> Power Off
Power On
Should briefly see the same erasing circle from Master Reset
You should now have mobile data again.
Step 7 - Clean Up
Get through setup screens
Enable ADB
Plug in
In Command Prompt ->
Code:
adb push path\to\twrp.img /sdcard/
adb shell
su
dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
Install Magisk Manager (it always needed a reboot after installing manager app to finish installing)
STOP HERE if you want a stock H933 ROM with unlocked bootloader, custom recovery, and root
IF YOU WANT TO FLASH A PIE ROM go to Settings -> Network -> Mobile network -> Advanced -> Access point names
Take a screenshot or write down every filed for every APN there, make sure to copy the screenshots off the device or at least to an external SD card
Step 8 - Flashing Pie ROMs
You will need:
Custom Pie ROM of choice
GAPPS (if needed for ROM)
Lunar Kernel
Magisk
The kernel you want is in the link to the Google Drive -> bleeding edge -> experimental_pie -> lunar_HMP-kernels_AOSP-Pie -> get the latest kernel for your ROM
You can also go elisa_EAS-kernels_AOSP-Pie for a power saving kernel (I have not tried this)
You don't need a custom kernel but every ROM is laggy and stutters without it
Reboot recovery
Make a backup of every partition of your working Stock H933 ROM (System Image may give an error, if so, deselect it)
Factory Reset
Format Data
Reboot Recovery
Flash ROM
Flash GAPPS (if needed)
Reboot Recovery
Flash kernel to boot partition
Reboot Recovery
Flash Magisk
Reboot System
You may lose data again (Bell customers will lose data, others may not). If you don't, go to Step 10.
For everyone else, people with no data, no SMS, no MMS, no calls, or anything carrier related, continue to the next step.
Step 9 - Fix APNs
NOTE I've only tried this with Bell but I don't see why it couldn't work with any other carrier
Install an explorer with root capabilities (make sure you've finished installing Magisk)
Copy "apns-conf.xml" from "/system/etc/" to an external SD card or to the Downloads folder
Copy it to your computer
Edit the file and change the APNs to be exactly what it showed in the APN menu of the stock rom
In my case for Bell:
Code:
<apn carrier="Bell" mcc="302" mnc="610" apn="pda.bell.ca" proxy="web.wireless.bell.ca" port="80" user="" password="" mmsc="http://mms.bell.ca/mms/wapenc" mmsproxy="web.wireless.bell.ca" mmsport="80" type="" />
<apn carrier="Bell Flex" mcc="302" mnc="610" apn="inet.bell.ca" proxy="" port="" user="" password="" mmsc="http://mms.bell.ca/mms/wapenc" type="default,supl,mms" />
Became:
Code:
<apn carrier="Bell Mobility" mcc="302" mnc="610" apn="pda.bell.ca" proxy="" port="" user="" password="" mmsc="http://mms.bell.ca/mms/wapenc" mmsproxy="" mmsport="" type="default,mms,supl,xcap" protocol="IPV4V6" roaming_protocol="IPV4" />
<apn carrier="Bell IMS" mcc="302" mnc="610" apn="ims" proxy="" port="" user="" password="" mmsc="" mmsproxy="" mmsport="" type="ims,vtims" protocol="IPV4V6" roaming_protocol="IPV4" />
NOTE I had to both add and delete fields
Copy modified "apns-conf.xml" back to the device
Delete the original file from "/system/etc/"
Copy the modified one to the same directory
Go to Settings -> Network -> Mobile network -> Advanced -> Access point names
In the three dot menu -> Reset to default
Select the right APN (I don't know what it is for every carrier, for Bell its the PDA one. I assume its the APN with "default" in the "APN type" field)
Reboot System
You should now have working data.
Step 10 - Profit and enjoy!
Thank you to:
@ChazzMatt
@seadersn
@cloud1250000
@Homer14061
and the people and teams whose posts and files I've linked here as well

Sorry if this is obvious and I missed it but, at the end of this do you end up with VoLTE/HD voice working on bell?
Currently have a h933 converted to 998 and rooted.

that's also a question I have and is the quad dac working?

bnevets27 said:
Sorry if this is obvious and I missed it but, at the end of this do you end up with VoLTE/HD voice working on bell?
Currently have a h933 converted to 998 and rooted.
Click to expand...
Click to collapse
cloud1250000 said:
that's also a question I have and is the quad dac working?
Click to expand...
Click to collapse
HI-Fi Quad DAC works on both Stock and Pie (at least Havoc, the only one I tested, but it should work for all).
VoLTE works on Stock but NOT on Pie.
Everyone asks about that in the ROM threads and it seems that LG doesn't use the Qualcomm drivers and the LG ones haven't been ported. There's a Magisk module to enable the VoLTE setting in the Mobile Data menu by editing the build.prop but it doesn't actually change anything.

can't we just grab another phone driver that is compatible with volte? like a one plus one phone I guess?

cloud1250000 said:
can't we just grab another phone driver that is compatible with volte? like a one plus one phone I guess?
Click to expand...
Click to collapse
No, it isn't that simple (as far as I'm aware, it's really out of my depth), so much so that there's still an ongoing bounty to get it working that's been up since June

Patched Software Not Working
I collected all the required software and patches. but when I run LGUP I get error stating "not support cross model download US998 to H933".
The thing I'm not understanding about the patches - they both include LGUP_common.dll, when I use the all variants dll, I get this error. "DLL for H93020d is invalid. Install vaild DLL package (*.msi) for the model". If both common.dll are to be used, then then they must be placed in different directories or renamed otherwise I'm just overwriting them. What am I doing wrong?
Please help.

ZoZat said:
I collected all the required software and patches. but when I run LGUP I get error stating "not support cross model download US998 to H933".
The thing I'm not understanding about the patches - they both include LGUP_common.dll, when I use the all variants dll, I get this error. "DLL for H93020d is invalid. Install vaild DLL package (*.msi) for the model". If both common.dll are to be used, then then they must be placed in different directories or renamed otherwise I'm just overwriting them. What am I doing wrong?
Please help.
Click to expand...
Click to collapse
The LGUP version I used is from the Frankenstein thread... Has the modded DLL file
Sent from my LG-H933 using Tapatalk

Night_1 said:
The LGUP version I used is from the Frankenstein thread... Has the modded DLL file
Sent from my LG-H933 using Tapatalk
Click to expand...
Click to collapse
Thanks. I'll report back and let you know how I made out.

I edited the guide to make patching LGUP more clear but yes, use the patched EXE and DLL from the Frankenstein thread

ZoZat said:
Thanks. I'll report back and let you know how I made out.
Click to expand...
Click to collapse
Nope. Didn't work. Still getting " Not support cross model download US988 to H933. I'm currently on a custom ROM that supports all variants. LGUP is correctly identifying my phone as US998. Is there a basic ROM for US998 I can flash before trying your solution? Maybe that with work?

ZoZat said:
Nope. Didn't work. Still getting " Not support cross model download US988 to H933. I'm currently on a custom ROM that supports all variants. LGUP is correctly identifying my phone as US998. Is there a basic ROM for US998 I can flash before trying your solution? Maybe that with work?
Click to expand...
Click to collapse
Yes, there's several TWRP flashable US998 stock "ROMs". See the US998 KDZ thread for links.

ChazzMatt said:
Yes, there's several TWRP flashable US998 stock "ROMs". See the US998 KDZ thread for links.
Click to expand...
Click to collapse
Can I use any of the flashable ROM's you referenced? Is there one in particular I should use?

ZoZat said:
Can I use any of the flashable ROM's you referenced? Is there one in particular I should use?
Click to expand...
Click to collapse
US998 20E was just before the recent massive audio changes, so should be safe.
Sent via open market LG US998 V30/V30+

ChazzMatt said:
US998 20E was just before the recent massive audio changes, so should be safe.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Phone successfully flashed to LG US998 20E. Started process again. Still getting same error, " Not support cross model download US998 to H933". I'm using all the required software, patches and kdz files. I've followed the directions (not that I've gotten very far). Phone was set in download mode. I tried running LGUP as administrator too - no luck. What could be causing this error? Any suggestions?

ZoZat said:
Phone successfully flashed to LG US998 20E. Started process again. Still getting same error, " Not support cross model download US998 to H933". I'm using all the required software, patches and kdz files. I've followed the directions (not that I've gotten very far). Phone was set in download mode. I tried running LGUP as administrator too - no luck. What could be causing this error? Any suggestions?
Click to expand...
Click to collapse
The symptoms are the same as if you were using regular LGUP instead of the Dev Patched LGUP. Regular LGUP would give you that type warning, when trying to cross flash another variant.
Dev Patched LGUP lets you do it. (Or should)
Sent via open market LG US998 V30/V30+

ChazzMatt said:
The symptoms are the same as if you were using regular LGUP instead of the Dev Patched LGUP. Regular LGUP would give you that type warning, when trying to cross flash another variant.
Dev Patched LGUP lets you do it. (Or should)
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
I've downloaded and installed the patches, which overwrites LGUP.exe and replaces the dll file in the common folder. When I launch the program I have all the extra radio buttons that the regular LGUP doesn't have. Doesn't that indicate I'm using Dev Patched LGUP? If not how can I verify?

ZoZat said:
I've downloaded and installed the patches, which overwrites LGUP.exe and replaces the dll file in the common folder. When I launch the program I have all the extra radio buttons that the regular LGUP doesn't have. Doesn't that indicate I'm using Dev Patched LGUP? If not how can I verify?
Click to expand...
Click to collapse
Try going into Download mode before opening LGUP.

ChazzMatt said:
Try going into Download mode before opening LGUP.
Click to expand...
Click to collapse
Tried that too. Didn't work.

ChazzMatt said:
Try going into Download mode before opening LGUP.
Click to expand...
Click to collapse
ZoZat said:
Tried that too. Didn't work.
Click to expand...
Click to collapse
What else can I try? What would happen if I flashed the Pie ROM for H930/H932 on top of US998? Can I not just use a flashable ROM to get to H933? Would it get stuck in boot loop or not boot at all?

downgrade from 10 to 9

Hey everyone, is it possible to downgrade to Android pie ?
Does simply flashing the build will do the trick ? Or it's impossible to go back to 9 ?
Thanks

youssefkr said:
Hey everyone, is it possible to downgrade to Android pie ?
Does simply flashing the build will do the trick ? Or it's impossible to go back to 9 ?
Thanks
Click to expand...
Click to collapse
I've read about several users going back to 9. However, it will take a full wipe and a clean flash of the factory image to do so :good:

I did downgrade to 9, full wipe, flashed twrp, in my case i needed root and magisk safetynet.

1902 said:
I did downgrade to 9, full wipe, flashed twrp, in my case i needed root and magisk safetynet.
Click to expand...
Click to collapse
Im debating rolling back, what rom did you settle on?

SageWilliams said:
Im debating rolling back, what rom did you settle on?
Click to expand...
Click to collapse
Latest original pie, rooted with latest magisk, if TWRP and safetynet were 100% working i would have stayed on A10, but till then i'm gonna stay on pie :angel:

I'm on 10 rooted, and can't unroot. Magisk won't uninstall from it's app. Tried to go back to 9, but it won't flash cleanly. I can sell the phone, but only if it's stock. 9 or 10, the buyer doesn't care. I can use a little help, please.
---------- Post added at 21:52 ---------- Previous post was at 21:33 ----------
How about, if I delete the sbin file in system/root, and then do a factory reset from the phone's settings?

1902 said:
I did downgrade to 9, full wipe, flashed twrp, in my case i needed root and magisk safetynet.
Click to expand...
Click to collapse
I don't need root, but please tell me how you downgraded from 10 back to 9. I really need to do this. Thanks

grunt0300 said:
I don't need root, but please tell me how you downgraded from 10 back to 9. I really need to do this. Thanks
Click to expand...
Click to collapse
Just Grab the pie factory image from https://developers.google.com/android/images
and follow the instruction on the developers' page, note that flashing this will wipe your device.
better to watch a tutorial online on how to flash a factory image :good:

1902 said:
Just Grab the pie factory image from https://developers.google.com/android/images
and follow the instruction on the developers' page, note that flashing this will wipe your device.
better to watch a tutorial online on how to flash a factory image :good:
Click to expand...
Click to collapse
Tried it, but no go. I get the command prompt box ok, but can't put anything into it.

grunt0300 said:
Tried it, but no go. I get the command prompt box ok, but can't put anything into it.[/QUOTE
I've done it by formatting data in twrp then flash pie ota, or flash the partitions (bootloader,radio,vendor) on both slots in fastboot then fastboot update (image-taimen-pq3a.190801.002.zip)
Click to expand...
Click to collapse

grunt0300 said:
Tried it, but no go. I get the command prompt box ok, but can't put anything into it.
Click to expand...
Click to collapse
Got it done. I had the files in the wrong place. It's all good now. Android 9, stock.

Im doing something wrong.
grunt0300 said:
Got it done. I had the files in the wrong place. It's all good now. Android 9, stock.
Click to expand...
Click to collapse
Hey I'm trying to downgrade myself and running into errors when trying to execute the flash-all command. Android 9 files are in the platform tools folder just like you would flash TWRP. First time downgrading. Is there a good tutorial...cause I followed the google tutorial and "flash-all" just sint working.

Driacas said:
Hey I'm trying to downgrade myself and running into errors when trying to execute the flash-all command. Android 9 files are in the platform tools folder just like you would flash TWRP. First time downgrading. Is there a good tutorial...cause I followed the google tutorial and "flash-all" just sint working.
Click to expand...
Click to collapse
Are you doing a clean install (leaving the -w intact)?
Do you have the latest SDK toolkit?
What errors are you running into?

Az Biker said:
Are you doing a clean install (leaving the -w intact)?
Do you have the latest SDK toolkit?
What errors are you running into?
Click to expand...
Click to collapse
Yes I'm using the latest SDK tools.
This is the error I recieved.
" flash-all : The term 'flash-all' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ flash-all
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (flash-all:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException"
Well the android updated to 10 on its own. I attempted to flash the newest version of Magisk onto it using TWRP. Now the phone just stays put at the google logo and wont boot further. It does boot into fastboot, So I figured I should just flash the older version back on. Also im on sailfish
---------- Post added at 11:06 PM ---------- Previous post was at 10:28 PM ----------
Also there is no "Flash-all" files that downloaded with the images. I have these files: Payload (Bin File), zipped combatability file, Meta file, care map and payload properties....

Driacas said:
Yes I'm using the latest SDK tools.
This is the error I recieved.
" flash-all : The term 'flash-all' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ flash-all
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (flash-all:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException"
Well the android updated to 10 on its own. I attempted to flash the newest version of Magisk onto it using TWRP. Now the phone just stays put at the google logo and wont boot further. It does boot into fastboot, So I figured I should just flash the older version back on. Also im on sailfish
---------- Post added at 11:06 PM ---------- Previous post was at 10:28 PM ----------
Also there is no "Flash-all" files that downloaded with the images. I have these files: Payload (Bin File), zipped combatability file, Meta file, care map and payload properties....
Click to expand...
Click to collapse
Did you unzip the factory image TWICE? Sounds like CMD isn't finding the flash-all file, which is in the folder after the second unzip.
As far as sailfish OS, I've never dealt with it so couldn't tell you one way of the other anything about it.

Driacas said:
Also there is no "Flash-all" files that downloaded with the images. I have these files: Payload (Bin File), zipped combatability file, Meta file, care map and payload properties....
Click to expand...
Click to collapse
Sounds like you downloaded the OTA file rather than the factory image file.