Develop Bugs

[A] Might be the answer for most of us regarding flashtool

So i check around the internet and found this. If you cant see the firmware content when selecting your ftf files. I found that by opening the ftf files using 7zip and deleting the for me it is the R800i_4.0.2.A.0.42_Generic_UK file inside then try to check whether the firmware content can be seen.
After deleting the file, the content can be seen. But i didnt try to flash it as i fear something might go wrong and hard bricked my phone. Anybody can test it out?
Idea from : lynxdog. ( I just played around the ftf folder to test it out whether can see the firmware content. )
Disclaimer :
Do it at your own risk.
I will not be held responsible for any damages caused to your smartphone. ( Test at your own risk )

AthrunIJ said:
So i check around the internet and found this. If you cant see the firmware content when selecting your ftf files. I found that by opening the ftf files using 7zip and deleting the for me it is the R800i_4.0.2.A.0.42_Generic_UK file inside then try to check whether the firmware content can be seen.
After deleting the file, the content can be seen. But i didnt try to flash it as i fear something might go wrong and hard bricked my phone. Anybody can test it out?
Idea from : lynxdog. ( I just played around the ftf folder to test it out whether can see the firmware content. )
Disclaimer :
Do it at your own risk.
I will not be held responsible for any damages caused to your smartphone. ( Test at your own risk )
Click to expand...
Click to collapse
As you have discovered the .ftf is simply a compressed file using a different file extension. The .sln files are also simply .img so you can use fastboot to flash these as required. I found that the UK generic 2.3.4 ftf file refused to decompress and be processed by flashtool so I manually extracted/unzipped the files and used fastboot to flash the kernel/system/userdata .sln to achieve what I wanted.

nurofenplus said:
As you have discovered the .ftf is simply a compressed file using a different file extension. The .sln files are also simply .img so you can use fastboot to flash these as required. I found that the UK generic 2.3.4 ftf file refused to decompress and be processed by flashtool so I manually extracted/unzipped the files and used fastboot to flash the kernel/system/userdata .sln to achieve what I wanted.
Click to expand...
Click to collapse
Same as the ICS Beta firmware i guess. As it came in a form of .img file instead of .ftf. file. So this firmware (uk generic 2.3.4) is only avail for unlock bootloader user. Bump!!!

sdojoin said:
Same as the ICS Beta firmware i guess. As it came in a form of .img file instead of .ftf. file. So this firmware (uk generic 2.3.4) is only avail for unlock bootloader user. Bump!!!
Click to expand...
Click to collapse
I'll check but it is a signed kernel and should flash just fine on a locked bootloader. I'll test it later this afternoon and confirm.

nurofenplus said:
I'll check but it is a signed kernel and should flash just fine on a locked bootloader. I'll test it later this afternoon and confirm.
Click to expand...
Click to collapse
If the .img file can be compile to be an .ftf file mybe u should try the Ics beta. If it can mybe it can flash on a locked bootloader as-well. If....

sdojoin said:
If the .img file can be compile to be an .ftf file mybe u should try the Ics beta. If it can mybe it can flash on a locked bootloader as-well. If....
Click to expand...
Click to collapse
The flashtool has an option under advance menu called bundle creation. I haven't used it but I'm guessing you point it at a folder with the collection of files (system, kernel etc...) and it does the rest.

nurofenplus said:
The flashtool has an option under advance menu called bundle creation. I haven't used it but I'm guessing you point it at a folder with the collection of files (system, kernel etc...) and it does the rest.
Click to expand...
Click to collapse
Ooo.. I haven't try it too.. Mybe i'll giv it a try when i get home. Thanks for the hint.

I think I'll try this myself as well!
Plus, I'm a locked user so I'm glad to try this out, I haven't thought about this idea. Lemme know how it goes for you, sdojoin!

Selim873 said:
I'm trying to download the beta but when I click the Accept button on the EULA, nothing happens, the reject button takes me back to the homepage obviously, but the accept button does nothing, does anybody have this mirrored?
Click to expand...
Click to collapse
I think the off. Beta link is dead after sony announce that play wont get any ics updte. Sory man..

sdojoin said:
I think the off. Beta link is dead after sony announce that play wont get any ics updte. Sory man..
Click to expand...
Click to collapse
That's okay, I found it though, but I have no idea how to work with the IMG files, as in, can't convert them into a group of .SIN_FILE_SET files to make them work with the Flash Tool bundle creator. So that won't work, because as far as I know, converting IMG to SIN isn't possible.

Selim873 said:
That's okay, I found it though, but I have no idea how to work with the IMG files, as in, can't convert them into a group of .SIN_FILE_SET files to make them work with the Flash Tool bundle creator. So that won't work, because as far as I know, converting IMG to SIN isn't possible.
Click to expand...
Click to collapse
Too many unknown words and language.... =.=, actually i post this to hlp some user who experience what i experience. the ftf files not showing firmware content and as a result cant flash it. so, basically, open the ftf files using 7zip or anything. then delete the file that has the same name as the ftf file itself. close the 'open archive' then voila working ftf file. then just follow the guide on using flashtool to flash. , learn it from many guys. And my utmost gratitude to the ppl who hlp.

AthrunIJ said:
Too many unknown words and language.... =.=, actually i post this to hlp some user who experience what i experience. the ftf files not showing firmware content and as a result cant flash it. so, basically, open the ftf files using 7zip or anything. then delete the file that has the same name as the ftf file itself. close the 'open archive' then voila working ftf file. then just follow the guide on using flashtool to flash. , learn it from many guys. And my utmost gratitude to the ppl who hlp.
Click to expand...
Click to collapse
Its already a diff discussion. Lol So it dont matter. If we cant flash this .ftf then just move on with a diff .ftf. No biggie.

The decrypt function in flashtool uses the temporary files that the official sony ericcson update tool creates in the background when upgrading your device. From these files flashtool extracts data and partition info etc... and generates the .sin files.
The bundle function then collects these files and creates a single .ftf file. So, I flashed the UK 2.3.3 and then relocked my bootloader (se update tool will not work with an unlocked bootloader). I then ran the sony update tool and let it download the latest 2.3.4 firmware and saved the files to another location.
Opened flashtool, ran the decrypt function using the folder I saved the se files to then the bundle function to create the ftf. I was able to successfully flash the new ftf file without issues. Anyway, probably a flashtool tutorial around somewhere.

Guide to Debranding / Rebranding Honor 6X

So I successful managed to rebrand my Indian Honor 6X (BLN-L22) to European Honor 6X (BLN-L21). This enabled me to use frequency band supported by EU version of the phone.
Following are the steps I followed:
1. Unlocked Bootloader : https://forum.xda-developers.com/honor-6x/how-to/how-to-unlock-bootloader-honor-6x-t3535321
2. Flash Custom Recovery:
i. Download TWRP for EMUI 4.1 or EMUI 5.0: https://forum.xda-developers.com/ho...k-recoveries-honor-6x-bln-l21-blnc00-t3632440
ii. In the folder where you have the twrp.img file (name may vary), shift+right click to open cmd prompt.
> adb reboot bootloader
> fastboot flash recovery twrp.img (or whatever is the name of your twrp img file)
3. Download Huawei Multi Tools and backup your oeminfo
4. Download oeminfo flashable zip attached with this post. Currently only EU and India are available. Request other users to share oeminfo of other regions
5. Using Firmware Finder, download the Stock ROM for the desired region. There will be two files, one update.zip file and another region specific file. Download both. Note: Only download Full Ota.
6. Extract the update.zip file and paste the UPDATE.APP file in a folder called "dload" inside an external sd card. Also copy the oeminfo zip file and region specific update zip file to an external sd card
7. Reboot to TWRP and flash oeminfo.zip
8. After oeminfo is flashed. Shutdown the phone and restart by holding vol up + vol down + power. You will enter update page and stock rom will be installed.
9. Once installed, you need to re-install TWRP recovery by following steps 1 and 2.
10. Finally, reboot to TWRP and install region specific update file.
You have now successfully debranded/ rebranded your Honor 6X
***** Edit ******
Uploaded the correct oeminfo file. Thanks @sanjay.rup for notifying the error

Excellent. Let me try myself to Debrand this weekend. Thanks for nice share buddy

uditshah said:
So I successful managed to rebrand my Indian Honor 6X (BLN-L22) to European Honor 6X (BLN-L21). This enabled me to use frequency band supported by EU version of the phone.
Following are the steps I followed:
....
You have now successfully debranded/ rebranded your Honor 6X
Click to expand...
Click to collapse
Hello,
I have see your zip file and :
oeminfo_HW_EU.zip => updater script => package_extract_file("oeminfo/eu/custom.bin", "/data/custom.bin");
BUT, folder inside zip is => oeminfo\in\xxxxx and custom.bin say "hw/in" (india)
oeminfo_HW_IN.zip => you have forget to remove oeminfo_HW_IN root folder
Conclusion: i haven't test, but i think this 2 zip file will never work ! BUT a BIG thx, i was looking for a indian "oeminfo" file for a friend, i will backup the "asian" oemfile this night, and flash indian oeminfo file manualy with him.
I can re-create the 2 zip file, i have BLN-L21 oeminfo (my phone for EUROPE), AND indian oeminfo "seems" to be good ! but this is your thread

sanjay.rup said:
Hello,
I have see your zip file and :
oeminfo_HW_EU.zip => updater script => package_extract_file("oeminfo/eu/custom.bin", "/data/custom.bin");
BUT, folder inside zip is => oeminfo\in\xxxxx and custom.bin say "hw/in" (india)
oeminfo_HW_IN.zip => you have forget to remove oeminfo_HW_IN root folder
Conclusion: i haven't test, but i think this 2 zip file will never work ! BUT a BIG thx, i was looking for a indian "oeminfo" file for a friend, i will backup the "asian" oemfile this night, and flash indian oeminfo file manualy with him.
I can re-create the 2 zip file, i have BLN-L21 oeminfo (my phone for EUROPE), AND indian oeminfo "seems" to be good ! but this is your thread
Click to expand...
Click to collapse
Share the Indian version files plz. I will probably go with that
---------- Post added at 02:57 PM ---------- Previous post was at 02:55 PM ----------
No custom bin file required

sanjay.rup said:
Hello,
I have see your zip file and :
oeminfo_HW_EU.zip => updater script => package_extract_file("oeminfo/eu/custom.bin", "/data/custom.bin");
BUT, folder inside zip is => oeminfo\in\xxxxx and custom.bin say "hw/in" (india)
oeminfo_HW_IN.zip => you have forget to remove oeminfo_HW_IN root folder
Conclusion: i haven't test, but i think this 2 zip file will never work ! BUT a BIG thx, i was looking for a indian "oeminfo" file for a friend, i will backup the "asian" oemfile this night, and flash indian oeminfo file manualy with him.
I can re-create the 2 zip file, i have BLN-L21 oeminfo (my phone for EUROPE), AND indian oeminfo "seems" to be good ! but this is your thread
Click to expand...
Click to collapse
You are right. I realized I uploaded the wrong files. I was using the EU version zip file to create the IN version zip and by mistake uploaded the working file.
Please do upload the oeminfo files you have. It would be super useful for the community

shashank1320 said:
Share the Indian version files plz. I will probably go with that
---------- Post added at 02:57 PM ---------- Previous post was at 02:55 PM ----------
No custom bin file required
Click to expand...
Click to collapse
Here you go

uditshah said:
Here you go
Click to expand...
Click to collapse
For BLN-L22?
And no need of custom bin?

shashank1320 said:
For BLN-L22?
And no need of custom bin?
Click to expand...
Click to collapse
I used the custom bin file. I have attached the Indian custom.bin file (extract the custom.zip file). If you are flashing using TWRP then you can directly flash the
oeminfo_HW_IN.zip file attached.
Hope this is useful

uditshah said:
I used the custom bin file. I have attached the Indian custom.bin file (extract the custom.zip file). If you are flashing using TWRP then you can directly flash the
oeminfo_HW_IN.zip file attached.
Hope this is useful
Click to expand...
Click to collapse
Ofcourse it is.
Thanks for the excellent share here

hi, i think ive made a huge mistake. i tried to modify the EU version of oeminfo by correcting the script ie giving it a correct path (replacing "in" with "eu) in updater script, it got successfully flashed but then the rom failed to install and as soon as the device rebooted system said something like "serious damage has occured" and then it wiped internal memory and locked the boot loader. i tried to install the rom (C185B361) which was working before via dload method but it keeps saying "version not compatible". i have access to fastboot, twrp and i also got backup of my original oeminfo. plz help me thank you

Khan001993 said:
hi, i think ive made a huge mistake. i tried to modify the EU version of oeminfo by correcting the script ie giving it a correct path (replacing "in" with "eu) in updater script, it got successfully flashed but then the rom failed to install and as soon as the device rebooted system said something like "serious damage has occured" and then it wiped internal memory and locked the boot loader. i tried to install the rom (C185B361) which was working before via dload method but it keeps saying "version not compatible". i have access to fastboot, twrp and i also got backup of my original oeminfo. plz help me thank you
Click to expand...
Click to collapse
Have you taken twrp backup?
Please restore if you have. Else due to flash, you model number is changed and you are not able to flash the original firmware.
May be you can try the other variant firmware which you flashed

Khan001993 said:
hi, i think ive made a huge mistake. i tried to modify the EU version of oeminfo by correcting the script ie giving it a correct path (replacing "in" with "eu) in updater script, it got successfully flashed but then the rom failed to install and as soon as the device rebooted system said something like "serious damage has occured" and then it wiped internal memory and locked the boot loader. i tried to install the rom (C185B361) which was working before via dload method but it keeps saying "version not compatible". i have access to fastboot, twrp and i also got backup of my original oeminfo. plz help me thank you
Click to expand...
Click to collapse
if it's old zip, rename "in/" folder with eu/ will not change file inside directory to "eu"; it's indian oemfile in L21 zip. Your are now brant to Indian rom. Redownload

sanjay.rup said:
if it's old zip, rename "in/" folder with eu/ will not change file inside directory to "eu"; it's indian oemfile in L21 zip. Your are now brant to Indian rom. Redownload
Click to expand...
Click to collapse
so if i get indian version of stock rom, install it via dload method, am i good to go?
P.S: this is a very unfortunate day as i removed my huge twrp backup in order to make space...so yeah a mess from my side.

Khan001993 said:
so if i get indian version of stock rom, install it via dload method, am i good to go?
P.S: this is a very unfortunate day as i removed my huge twrp backup in order to make space...so yeah a mess from my side.
Click to expand...
Click to collapse
if you have flash indian oeminfo file, you will be able to dload indian rom (C675).
If you flash your backup oeminfo file, you will be able to dload your old region rom file !

So, successfuly brant Asia to Indian with zip extracted oeminfo file. C636B372 => C675B340 via dload. VoLTE Jio SIM working for my friend's phone.
Download zip is not updated for me.
Waiting for him, to upload Asian oeminfo.

sanjay.rup said:
So, successfuly brant Asia to Indian with zip extracted oeminfo file. C636B372 => C675B340 via dload. VoLTE Jio SIM working for my friend's phone.
Download zip is not updated for me.
Waiting for him, to upload Asian oeminfo.
Click to expand...
Click to collapse
Did you rebranded your friend's phone?

shashank1320 said:
Did you rebranded your friend's phone?
Click to expand...
Click to collapse
YES. He was ASIAN C636 B372 (B360 before). Dload Indian C675 B340 failed !
Replace oeminfo file, with indian one (extracted from zip), and dload Indian C675 B340 flash success. VoLTE with JIO Sim work directly !

Khan001993 said:
hi, i think ive made a huge mistake. i tried to modify the EU version of oeminfo by correcting the script ie giving it a correct path (replacing "in" with "eu) in updater script, it got successfully flashed but then the rom failed to install and as soon as the device rebooted system said something like "serious damage has occured" and then it wiped internal memory and locked the boot loader. i tried to install the rom (C185B361) which was working before via dload method but it keeps saying "version not compatible". i have access to fastboot, twrp and i also got backup of my original oeminfo. plz help me thank you
Click to expand...
Click to collapse
Flash the attached oeminfo file using TWRP. It is the correct version of the EU oeminfo. Flash the ROM BLN-L21C10B131. It should work.

sanjay.rup said:
YES. He was ASIAN C636 B372 (B360 before). Dload Indian C675 B340 failed !
Replace oeminfo file, with indian one (extracted from zip), and dload Indian C675 B340 flash success. VoLTE with JIO Sim work directly !
Click to expand...
Click to collapse
Perfect. Can you ask your friend to upload ASIAN oeminfo

Get as many files as we can...it will be helpful for sure. Repository thread will be updated soon with all these info with proper credit :good:
Good work guys

where to get MIFLASH tool

im trying to get the tools recomended in multiple guides, for restoreing phone to stock.
I mean the MI-Flash tool. The links from mi-community all lead to "404 page not found"
I have found the fastboot rom. The archive has windows and linux scripts (*.bat, & *.sh) so is the MIFlash tool even needed?
I found the tool on mi-globe.com, but cant tell if its official.

mrmazak said:
im trying to get the tools recomended in multiple guides, for restoreing phone to stock.
I mean the MI-Flash tool. The links from mi-community all lead to "404 page not found"
I have found the fastboot rom. The archive has windows and linux scripts (*.bat, & *.sh) so is the MIFlash tool even needed?
I found the tool on mi-globe.com, but cant tell if its official.
Click to expand...
Click to collapse
Go to https://www.xiaomiflashtool.com/.
Download the version you like. It's not an .msi installer but a zip package. The Mi community has removed the msi installer from their server. You can use the miflash tool from XiaomiFlashTool or the msi installer from me. I have downloaded from Mi community 3 months earlier. I will give you Gdrive link if you need.

mrmazak said:
im trying to get the tools recomended in multiple guides, for restoreing phone to stock.
I mean the MI-Flash tool. The links from mi-community all lead to "404 page not found"
I have found the fastboot rom. The archive has windows and linux scripts (*.bat, & *.sh) so is the MIFlash tool even needed?
I found the tool on mi-globe.com, but cant tell if its official.
Click to expand...
Click to collapse
here's the link for official mi flash... yes you don't necessarily need mi flash just run the flash_all.bat and you'll be good to go

Look like the download link of MiFlash is fixed. I sent a thread to Mi community.
The link for official MiFlash tool is shown below:
https://download.appmifile.com/images/2019/07/01/09cdc3a7-5a11-42aa-81f4-be27fe12ce80.msi
EDIT: The msi link maybe unstable. Here is the latest download link:
https://cdn.alsgp0.fds.api.mi-img.com/micomm/MiFlash2020-3-14-0.rar

Is it possible to use mi flash with the bootloader blocked?

marlon_cazais said:
Is it possible to use mi flash with the bootloader blocked?
Click to expand...
Click to collapse
yes, mi_flash does only revert to stock firmware if needed

Installing ROM failed "Antirollback check error"

I'm trying to install the lastest room on my xiaomi redmi note 8 pro GLOBAL.
so when I go and check the current rollback version on my phone I get this.
Command: fastboot getvar anti
Ouput: anti: 1
The latest room available in the xiaomi page is V11.0.5.0.QGGMIXM when cheking the rollback version on the room I get this (go to the folder then open in a text editor flash_all.bat).
CURRENT_ANTI_VER=0
So I'm not able to flash the room via mi flash tool. I get this error
Current device antirollback version is greater than this pakcage
Where can I get the correct room?
PD: I'm stucked in a bootloop so re installing a stock room is the only option to save my phone.

This error happens because the folder path has become too long. Copy the folder to the root of the disk and delete the folder name after the model and variant of the rom. Leave something like that. Local disk D - rom PGGEUXM and the files are already inside this folder. Do not modify anything. Just extract the files from the fastboot rom and place them in a folder where the folder path is as short as possible. Hug (sorry for my English. Because I used the translator.

Solution
joaokemmer said:
This error happens because the folder path has become too long. Copy the folder to the root of the disk and delete the folder name after the model and variant of the rom. Leave something like that. Local disk D - rom PGGEUXM and the files are already inside this folder. Do not modify anything. Just extract the files from the fastboot rom and place them in a folder where the folder path is as short as possible. Hug (sorry for my English. Because I used the translator.
Click to expand...
Click to collapse
Thanks!, after cheking all over internet found that as you said this is the actual issue, I placed the room folder in C:// and mi flash tool as well and managed to flash the room.
I got this error during the flashing
error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done
But as I read this error means nothing since my actual phone is working now. Hope this can help others.

Question Problems with the connectivity on Poco F3 LineageOS + Magisk

I using my Poco F3 since a few month with lineageOS and I'm quite happy. The only problem: Wify and mobile data. Most of the time there is an exclamation mark in the topline on the icons for wify and mobile data.
I tried all the normal stuff:
– reboot the mobile phone (which sometimes really works)
– reboot thr router
– check the settings
– swap the sim cards (because sometimes I was only able to call somebody with one of the sim cards
With the last update of lineageOS it seems that the sim cards work again properly for calls, but not for mobile data.
Despite the exclamation marks surfing und emails works fine. I just can't synchronise my calendar via DAVdroid.
Any hint is appreciated.

are you using the recommended firmware version?
i had some issues with sounds with newer firmware versions

Good question.
I didn't change the firmware. How can I check, which version is runing on my device?

Idk how you'd check the firmware version but you could install the latest firmware for your region regardless.
Or if LineageOS recommends a specific FW version, install that instead.
Xiaomifirmware.com is one place where you can find official MIUI ROM versions and Firmware (/vendor).
You can just install it in Recovery, install itself takes a couple of seconds since Firmware is around 100 MB.

Isn't there an official site to download the firmware?

RunnersHai said:
Isn't there an official site to download the firmware?
Click to expand...
Click to collapse
xiaomifirmwareupdater.com is a reputable source for official Xiaomi FW and ROMs.
Xiaomi do have a website where you can DL ROMs but it's bad.

Perfect, thx a lot. I will try,if it works. Keep fingers crossed ;-D

Sorry, I don't get any further. I only find complete Roms with 3.1 GB and more. But not a vendor with the code POCO F3 Global - V13.0.3.0.SKHMIXM as mentioned on the website of Lineageos.org (https://wiki.lineageos.org/devices/alioth/fw_update). Even the direct link downloads a complete Rom.
And can I install the vendor with my linux computer or should I switch windows and the mi-tool as mentioned on some websites?
Thanks for your help.

Okay, I'm a little bit further. As far as I understood it. I download the whole Rom but install just a few parts via adb. Following the instructions here: https://wiki.lineageos.org/devices/alioth/fw_update
I should install the payload-dumper-go to unpack the zip-file of the ROM. But I don't know how to start the programm
I downloaded it from github for Linux, but I don't know how to get any further.

RunnersHai said:
Okay, I'm a little bit further. As far as I understood it. I download the whole Rom but install just a few parts via adb. Following the instructions here: https://wiki.lineageos.org/devices/alioth/fw_update
I should install the payload-dumper-go to unpack the zip-file of the ROM. But I don't know how to start the programm
I downloaded it from github for Linux, but I don't know how to get any further.
Click to expand...
Click to collapse
You're right. I checked out that website and those links are indeed full Recovery MIUI ROMs, not just firmware.
Those instructions show you how to manually flash just the firmware from a ROM.zip
However, you don't need to do that. Here is a link to just the firmware for that exact ROM:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
v13.0.3 seems rather old to me, but if it's their recommendation, then I guess go ahead. After all you simply want these problems to go away.
How to flash:
Simply boot into Recovery and do ADB Sideload
"adb sideload firmware.zip"
If you want to use the Payload Dumper anyway:
In your Linux Machine, open the Payload Dumper folder,
right-click an empty space in the folder, click "Open in Terminal",
type "payload-dumper-go -o . " and drag & drop the MIUI_ROM.zip into the Terminal (this will autofill the path to that ROM),
Hit Enter.
Then, open the created folder where all the extracted partition-images are. Open that folder in Terminal, and do the fastboot commands listed on the LineageOS-website that you linked to me.

Great thanks a lot for your help. New stuff to learn – that's great.
Unfortunately I figured out that the reason for the problems could be a wrong setting in my AFWall+. I will double check that and if it's not the reason, I will follow your instructions. Thanks a lot for your work – awesome.

heres the firmware archive,no need for full rom and fastboot commands
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com