Guide to Debranding / Rebranding Honor 6X - Honor 6X Guides, News, & Discussion

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

Related

[Q] Please HELP! P6U06 B107, how to update to 4.4.2

Hi i am currently using Huawei Ascend P6,
my version was P6-U06, B107, and can anyone teach me how to update it to 4.4.2 android kit kat?
Please guide.. Thanks!!!
Hi! You should install b132 firmware (extract downloaded file>make 'dload' folder on your external sd card and put UPDATE.APP into dload then go to settings>about phone>system updates> make backup(optional) and apply and the phone will do the rest (cca15min)) and when you are on b132 do the same with b510 firmware. You can download it from offical huawei site or from here http://forum.xda-developers.com/show....php?t=2782496
n00b_user said:
Hi! You should install b132 firmware (extract downloaded file>make 'dload' folder on your external sd card and put UPDATE.APP into dload then go to settings>about phone>system updates> make backup(optional) and apply and the phone will do the rest (cca15min)) and when you are on b132 do the same with b510 firmware. You can download it from offical huawei site or from here http://forum.xda-developers.com/show....php?t=2782496
Click to expand...
Click to collapse
that link is not available please any other mirrors for b510 ktkt
vennyvenance said:
that link is not available please any other mirrors for b510 ktkt
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2782496
---------- Post added at 01:21 PM ---------- Previous post was at 01:06 PM ----------
https://mega.co.nz/#!kd0kQJba!iQJsijbnwWnyH2zKBPxu35MbO7xBS3cFlzTH4LFYY70
If you get an error FAIL try this one.
Errors
Sent from my HUAWEI P6-U06 using XDA Free mobile app
Ascend P6U06 update from B107 to B510
n00b_user said:
Hi! You should install b132 firmware (extract downloaded file>make 'dload' folder on your external sd card and put UPDATE.APP into dload then go to settings>about phone>system updates> make backup(optional) and apply and the phone will do the rest (cca15min)) and when you are on b132 do the same with b510 firmware. You can download it from offical huawei site or from here http://forum.xda-developers.com/show....php?t=2782496
Click to expand...
Click to collapse
Hi. I am currently using ascend B132 android version 4.2.2 . Initially I had the same issue, I was on B107 and wanted to update it to Kitkat inorder to gain some advancements regarding camera lens. SO I read your post and followed all of your steps. I extracted the B132.zip file and moved the UPDATE.APP file to a folder named dload in my SD card, installed it and it worked. (Y) But now that I have to upgrade to B510, I have no clear instructions after doing hours of research. You stated to follow the same method for the upgradation of B510 but many sites say that it should not be extracted and just rename it to UPDATE.ZIP and paste it to the dload folder. Considering the fact that i still have my UPDATE.APP file (from the previous step of upgrading to B132) in the dload folder, I should paste the UPDATE.ZIP (for B510) in the same folder or remove the UPDATE.APP
I have tried both methods, but as one site says when UPDATE.APP is not present in the folder containing UPDATE.ZIP, android fails to recognize any update and it aborts. whereas, when UPDATE.APP is there too, it just installs the B132 (from the update.app) again and kinds of overlooks the update.zip for B510 and hence there is no update to B510. Kindly, provide me with the steps of installing B510. I have listed all of the problems I am experiencing.
There shouldnt be zip files in the folder. Extract the update.app from the zip file for b510 place it in the dload folder on the sd card an make the update.
Sent from my SM-G850F
tileeq said:
There shouldnt be zip files in the folder. Extract the update.app from the zip file for b510 place it in the dload folder on the sd card an make the update.
Sent from my SM-G850F
Click to expand...
Click to collapse
The zip file of B510 just don't get extracted and an error occurs. Furthermore all of the other websites states not to extract it, just to rename it as update.zip and put it in dload. does not works.
Dying to update.
Let me check if i have the b510 or b512 update in my comp and ill try to upload it. Then you can work as i said before.
Sent from my SM-G850F
https://mega.nz/#!wwE0iA5T!az1V22ZO_9oBSdcmL7X6Fk7CIWBLEg2rEVsPJCmK_d8
Sent from my SM-G850F
About the download link
Sent from my SM-G850F[/QUOTE]
Thankyou so much. But i think I downloaded from the very same webpage. However, I will give it a try.
Please illustrate clearly whether I have to zip the 510 file. And secondly, The update app file of B132 shouldn't be placed in dload while upgrading?
AND MOST IMPORTANTLY, DOES THIS FILE GETS EXTRACTED?
From the link i gave you, you should be able to get a zip file. Extract the zip and see if there is a file called updeta.app. Once you have that file place it in dload folder on sd card and start the update with the three button method.
Sent from my SM-G850F
tileeq said:
From the link i gave you, you should be able to get a zip file. Extract the zip and see if there is a file called updeta.app. Once you have that file place it in dload folder on sd card and start the update with the three button method.
Sent from my SM-G850F
Click to expand...
Click to collapse
File can't be extracted. It says unknown method in dload/UPDATE.APP
Really can't help myself. Have searched nearly thousand blogs, all say not to extract it. But that method don't work as well. :crying:
billmunawar123 said:
File can't be extracted. It says unknown method in dload/UPDATE.APP
Really can't help myself. Have searched nearly thousand blogs, all say not to extract it. But that method don't work as well. :crying:
Click to expand...
Click to collapse
Ok then are you willing to try b708?
Sent from my SM-G850F
tileeq said:
Ok then are you willing to try b708?
Sent from my SM-G850F
Click to expand...
Click to collapse
The User-interface seems pretty good. Please tell me that is this release of B708 for P6 huawei's an official one by the makers of huawei?
Secondly, Is it lollipop or Kitkat?
Lastly, I'm concerned with the speed of the phone, Will it be affected largely?
And If we're good to go, Kindly guide me with the steps and also the requirements for Installing this B708. And most importantly for upgradation of p6 to B708 , it should be running a particular firmware first like B707 but I have B132 so what I have to do. Stuck so badly,
Regards
Well first, it is an official update from huawei but it was only released in china. Because of that you will find some chinese apps in the system but they wont make any problems for the experience with working on the phone. It is kitkat since our beloved P6 didnt get lolipop update and probably wont in future. About performance it will show some improvements, but thats my opinion since ive read on this forum that some arent satisfied with the overall update. And for the proccess of upgrading it is written on their official site that the recomended steps are that you get b508sp2 first and then go to b708. As for b707 i wouldnt suggest it since it still has bugs.
Sent from my SM-G850F
---------- Post added at 00:25 ---------- Previous post was at 00:21 ----------
Let me get working links and ill post it here. For both b508sp2 and b708
Sent from my SM-G850F
tileeq said:
Well first, it is an official update from huawei but it was only released in china. Because of that you will find some chinese apps in the system but they wont make any problems for the experience with working on the phone. It is kitkat since our beloved P6 didnt get lolipop update and probably wont in future. About performance it will show some improvements, but thats my opinion since ive read on this forum that some arent satisfied with the overall update. And for the proccess of upgrading it is written on their official site that the recomended steps are that you get b508sp2 first and then go to b708. As for b707 i wouldnt suggest it since it still has bugs.
[/COLOR]Let me get working links and ill post it here. For both b508sp2 and b708
Okay Thanks for sharing all the information. And lastly do you have to be on a specific Firmware as well for upgrading to b508sp2?
Waiting for the working links and the method of installation.
Click to expand...
Click to collapse
How to Update
Flashing this update requires your phone to be already running B706/B707 EMUI 3.0 developmental firmware or B508 (U06)/ B508SP02 (T00) or B508SP03 (C00) EMUI 2.0 stable firmware on board.
Download the appropriate firmware on your computer and extract it.
Connect your Ascend P6 to the computer in MTP mode over a USB connection.
Format the SD Card in FAT32 filesystem and make sure it has at least 2GB of free space.
Copy the “Update.app” package to “dload” folder of your SD Card.
Disconnect all the cables and completely turn off your phone.
Reboot into automatic upgrade mode by holding Volume Up + Volume Down + Power button for about 10 seconds. Release the Power button when your phone vibrates.
Let go of the Volume keys once your device begins to perform the upgrade.
It’ll take a few seconds to finish the process. Once you’re done reboot your phone normally and enjoy the update.
If SD Card update fails, transfer the dload folder with the update.app file in the internal storage and repeat the steps for updating.
https://mega.nz/#!DswQlAgJ - this is the first update file. In case it requires a key to download use this - !ig-p25rO1ev3CYBk6Js1LkaQ7nGT09-TDXpcaZFZI7I
https://mega.nz/#!ToIikSzR - this is the second. Same here - !lJWmd5KNEU9SravuHZg-pqGdJNGkd3xIv8lzYA58s3Y

[Guide] Root Oppo F1s(A1601) + SuperSU without custom recovery or unlocked bootloader

EDIT: This root method has been outdated, see the newer guide instead https://forum.xda-developers.com/android/general/tutorial-root-oppo-f1s-flashtool-6-0-t3651220
Why I made this tutorial:
Recently some members claimed that KingRoot is not working for Oppo F1s(A1601) anymore, I assume it's because Kingroot uses cloud based root method, means Kingroot downloads root package and command from cloud and execute on your phone. Maybe the problem was caused by the change of their server, some configuration has been replaced? At this time, I still have a working root method working now, so I would like to share it with everyone Also, you can follow this guide to get rid of the superuser App from those android root exploit app and use SuperSU.
In short, this tutorial tells:
1.How to Root Oppo F1s(A1601) with KingoRoot.(Though cloud based root App Kingroot is not working at this period but KingoRoot the offline one is still working)
2.Though KingoRoot prevent you to switch to other superuser App, we can still replace it with SuperSU with few steps, no custom recovery needed.
****NOTE****
There're various version of KingoRoot apk over the Internet, use the APK version I provided at attachment can guarantee there're no unexpected errors.
The script to replace kingo root was based on the one here but with a little modification, I've added a infinite loop for the script because KingoRoot cause a force reboot(soft reset) right after you delete root from the app, I assume its because KingoRoot want to prevent you to replace it. A infinite loop can make sure the file copying action has been done before your phone reboot.
Steps to Root F1s and Install SuperSU:
1.Install android terminal from Google Play: https://play.google.com/store/apps/details?id=jackpal.androidterm
2.Download the attachment, extract the zip archive, you get an APK "KingoRoot.apk" and a folder "rmkingo", copy the APK and the folder to your Internal storge(Sdcard)
3.Use any file management App to open KingoRoot.apk and install KingoRoot.apk
4.Open KingoRoot and click "one click root" then wait it to obtain root
5.After root succeeded, Open previous installed "Terminal Emulator for Android" and type
Code:
su
. Now KingoRoot's Superuser should pop up and ask you if you want to grant root access, allow it.
6.Now change terminal directory to the script folder, terminal type
Code:
cd /sdcard/rmkingo
7.Now execute the first script, terminal type
Code:
sh step0.sh
8.If there's no error on the previous action, Now proceed to execute the second script which is an infinite loop, you might see infinite error message after you executed it, terminal type
Code:
sh step1.sh
9.Now make sure the Terminal emulator is still open and the script is still running in background, just open SuperUser(installed by KingoRoot), find and click "Remove root" in the option of the App.
10.Your phone should be forced reboot now, after reboot, install SuperSU from google play: https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=zh_TW
11.Open SuperSU and update su binary file with normal mode and wait, it should finish in 2-3 minutes.
12.Hit thanks(My pleasure)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
above method has been confirmed working with the latest rom from my region,(date 2017/02/12 still working)
Rom: A1601_TW_11_A.17_161003
I am on build a1601ex_11_a27_170111
its currently letest update in india
sagargjasani264 said:
I am on build a1601ex_11_a27_170111
its currently letest update in india
Click to expand...
Click to collapse
Wow, Taiwan haven't receive any update since October........Looks like the rom of our region is terribly outdated,lol
A lot of people complaint on oppo forum of our region why there're no updates........
Is it method work for the rom from india?
evilhawk00 said:
wow, taiwan haven't receive any update since october........looks like the rom of our region is terribly outdated,lol
a lot of people complaint on oppo forum of our region why there're no updates........
Is it method work for the rom from india?
Click to expand...
Click to collapse
kingoroot is on 90% since last 20min
---------- Post added at 12:22 PM ---------- Previous post was at 12:10 PM ----------
sorry bro but kingoroot faild...
Sorry kingoroot failed error code : 0x196514
Lyes2 said:
Sorry kingoroot failed error code : 0x196514
Click to expand...
Click to collapse
Hi, I assume you have to downgrade your rom. Find a older version of your rom, flash it via OPPO stock recovery and this method will work.
In my region, Taiwan's newest rom date is 2016 October, so this method work. OPPO might fixed this CVE exploit in their new rom.
The rom I currently use can be downloaded from OPPO Taiwan website, however I'm not sure if it can work on your device, so you might need to find an older version of your region
You can try to get root with older firmware, flash twrp recovery with root app, such as rashr,then once you have twrp recovery, you can flash the new OTA update package, but be sure to modify the update package so you will not loose root after update. However, I think just stick with older firmware will be easier
Failed
Directory not found bro
evilhawk00 said:
Hi, I assume you have to downgrade your rom. Find a older version of your rom, flash it via OPPO stock recovery and this method will work.
In my region, Taiwan's newest rom date is 2016 October, so this method work. OPPO might fixed this CVE exploit in their new rom.
The rom I currently use can be downloaded from OPPO Taiwan website, however I'm not sure if it can work on your device, so you might need to find an older version of your region
You can try to get root with older firmware, flash twrp recovery with root app, such as rashr,then once you have twrp recovery, you can flash the new OTA update package, but be sure to modify the update package so you will not loose root after update. However, I think just stick with older firmware will be easier
Click to expand...
Click to collapse
what kind of modification do you exactly need to do to the update package to not loose root after update?
ngoralph said:
what kind of modification do you exactly need to do to the update package to not loose root after update?
Click to expand...
Click to collapse
I made one and got root with A27 , all you need is a twrp and a twrp flashable firmware zip.
Here's what I did,first I found that the TWRP by @BouyaPK did not have the same device model settings in comparison with the stock recovery, so I made a little modification to his TWRP image, now the offical firmware zip can pass Device detection test.
!!Before doing it , make sure you have flashed the modified recovery(the one from attachment) to your phone, official firmware is only flashable via this modified recovery and stock recovery
Download here
View attachment OPPO_F1s_twrp3.0_modified_devicemodel.zip
this is the example with the ota update package (A19 to A27 upgrade package around 150mb via coloros update manager app)
Now lets start to modify official firmware, follow my steps:
1.extract the newest official firmware zip.
2.now open the extracted folder, navigate to \META-INF\com\google\android\
3.find the file updater-script and open it with text editor( I suggest NotePad++)
4.you'll find a lot of lines start with apply_patch(xxxxx), remove the one with this file "/system/recovery-from-boot.p"
5.(if needed) also remove boot image sha1 check, in my case I have magisk installed, my boot image do not have the same sha1 value with stock boot image, so I found the line that checkes boot.img and remove it
6.done the file edit and save the file
7.repack it back to a zip file and sign the package with test keys
How to sign?
1.Download the sign package from attachment
2.have Java installed on your PC
3.Open a terminal at the same location with the keys and signapk.jar
4.terminal type
Code:
java -jar signapk.jar -w platform.x509.pem platform.pk8 my_modified_firmware.zip my_modified_firmware-signed.zip
8.install with twrp and you still have twrp exist, flash supersu zip or magisk zip
above is the way to modify a PATCH zip ota file, if you are modifying a full package, which may be easier,
the full package's update script write full image to phone instead, so you just need to modify the image in the ota package.
all you just have to make sure the new firmware do not replace twrp with stock recovery, so
1.try to extract the image in the package and modify the image file, remove files such as "recovery-from-boot.p" from the image then rebuild the image and calculate the new sha1 value of the new image(CarlivImageKitchen is a good tool to rebuild image)
2.replace the old sha1 hash in updater-script, repack and sign the zip.
3.flash with twrp
4.flash superSu zip or magisk zip after the firmware flash with twrp can get root.
evilhawk00 said:
I made one and got root with A27 , all you need is a twrp and a twrp flashable firmware zip.
Here's what I did,first I found that the TWRP by @BouyaPK did not have the same device model settings in comparison with the stock recovery, so I made a little modification to his TWRP image, now the offical firmware zip can pass Device detection test.
!!Before doing it , make sure you have flashed the modified recovery(the one from attachment) to your phone, official firmware is only flashable via this modified recovery and stock recovery
Download here
this is the example with the ota update package (A19 to A27 upgrade package around 150mb via coloros update manager app)
Now lets start to modify official firmware, follow my steps:
1.extract the newest official firmware zip.
2.now open the extracted folder, navigate to \META-INF\com\google\android\
3.find the file updater-script and open it with text editor( I suggest NotePad++)
4.you'll find a lot of lines start with apply_patch(xxxxx), remove the one with this file "/system/recovery-from-boot.p"
5.(if needed) also remove boot image sha1 check, in my case I have magisk installed, my boot image do not have the same sha1 value with stock boot image, so I found the line that checkes boot.img and remove it
6.done the file edit and save the file
7.repack it back to a zip file and sign the package with test keys
How to sign?
1.Download the sign package from attachment
2.have Java installed on your PC
3.Open a terminal at the same location with the keys and signapk.jar
4.terminal type
8.install with twrp and you still have twrp exist, flash supersu zip or magisk zip
above is the way to modify a PATCH zip ota file, if you are modifying a full package, which may be easier,
the full package's update script write full image to phone instead, so you just need to modify the image in the ota package.
all you just have to make sure the new firmware do not replace twrp with stock recovery, so
1.try to extract the image in the package and modify the image file, remove files such as "recovery-from-boot.p" from the image then rebuild the image and calculate the new sha1 value of the new image(CarlivImageKitchen is a good tool to rebuild image)
2.replace the old sha1 hash in updater-script, repack and sign the zip.
3.flash with twrp
4.flash superSu zip or magisk zip after the firmware flash with twrp can get root.
Click to expand...
Click to collapse
Can you send me a stock recovery for Oppo F1s or Color Os 3.0 version
[email protected]
I want ask to my friend to build the custom rom with latest version of TWRP.
Ananaqil12 said:
Can you send me a stock recovery for Oppo F1s or Color Os 3.0 version
[email protected]
I want ask to my friend to build the custom rom with latest version of TWRP.
Click to expand...
Click to collapse
If you want stock recovery image, check my reply here https://forum.xda-developers.com/showpost.php?p=71006625&postcount=26
evilhawk00 said:
I made one and got root with A27 , all you need is a twrp and a twrp flashable firmware zip.
Here's what I did,first I found that the TWRP by @BouyaPK did not have the same device model settings in comparison with the stock recovery, so I made a little modification to his TWRP image, now the offical firmware zip can pass Device detection test.
!!Before doing it , make sure you have flashed the modified recovery(the one from attachment) to your phone, official firmware is only flashable via this modified recovery and stock recovery
Download here
View attachment 4137856
this is the example with the ota update package (A19 to A27 upgrade package around 150mb via coloros update manager app)
Now lets start to modify official firmware, follow my steps:
1.extract the newest official firmware zip.
2.now open the extracted folder, navigate to \META-INF\com\google\android\
3.find the file updater-script and open it with text editor( I suggest NotePad++)
4.you'll find a lot of lines start with apply_patch(xxxxx), remove the one with this file "/system/recovery-from-boot.p"
5.(if needed) also remove boot image sha1 check, in my case I have magisk installed, my boot image do not have the same sha1 value with stock boot image, so I found the line that checkes boot.img and remove it
6.done the file edit and save the file
7.repack it back to a zip file and sign the package with test keys
How to sign?
1.Download the sign package from attachment
2.have Java installed on your PC
3.Open a terminal at the same location with the keys and signapk.jar
4.terminal type
Code:
java -jar signapk.jar -w platform.x509.pem platform.pk8 my_modified_firmware.zip my_modified_firmware-signed.zip
8.install with twrp and you still have twrp exist, flash supersu zip or magisk zip
View attachment 4137905
above is the way to modify a PATCH zip ota file, if you are modifying a full package, which may be easier,
the full package's update script write full image to phone instead, so you just need to modify the image in the ota package.
all you just have to make sure the new firmware do not replace twrp with stock recovery, so
1.try to extract the image in the package and modify the image file, remove files such as "recovery-from-boot.p" from the image then rebuild the image and calculate the new sha1 value of the new image(CarlivImageKitchen is a good tool to rebuild image)
2.replace the old sha1 hash in updater-script, repack and sign the zip.
3.flash with twrp
4.flash superSu zip or magisk zip after the firmware flash with twrp can get root.
Click to expand...
Click to collapse
There are no lines that say apply patch
diosdetiempo said:
[/HIDE]
There are no lines that say apply patch
Click to expand...
Click to collapse
As I mentioned, only the small OTA Update package(smaller than 300MB) extracted from Built in update manager App has the line apply patch.
You are using a full package which is another situation.
If you have the full ota firmware downloaded from official website, you can try the follow steps
1.first make a nandroid backup of the old 5.1, make sure you can always restore your phone with backup
2.flash the official firmware zip with the twrp I attach( if any error occurred,do not reboot ,restore your phone with nandroid backup, also write down the error, and see which image file does not have the match SHA1, calculate and modify the sha1 of that line)
3.if step 2 succed ,do not reboot flash superSU zip file
4reboot, you may have superSU and your twrp may be replaced by stock recovery, use rashr flash twrp back again since you have root
evilhawk00 said:
As I mentioned, only the small OTA Update package(smaller than 300MB) extracted from Built in update manager App has the line apply patch.
You are using a full package which is another situation.
If you have the full ota firmware downloaded from official website, you can try the follow steps
1.first make a nandroid backup of the old 5.1, make sure you can always restore your phone with backup
2.flash the official firmware zip with the twrp I attach( if any error occurred,do not reboot ,restore your phone with nandroid backup, also write down the error, and see which image file does not have the match SHA1, calculate and modify the sha1 of that line)
3.if step 2 succed ,do not reboot flash superSU zip file
4reboot, you may have superSU and your twrp may be replaced by stock recovery, use rashr flash twrp back again since you have root
Click to expand...
Click to collapse
It worked!
Here's a little guide
1) Put your TWRP, SuperSU and Android 6.0 Oppo F1S ROM onto SD card
2) Use Flashify to flash TWRP
3) Reboot into TWRP recovery
4) Flash Android 6.0 F1S ROM
5) Flash SuperSU
6) Reboot phone and you should be good to go
evilhawk00 said:
As I mentioned, only the small OTA Update package(smaller than 300MB) extracted from Built in update manager App has the line apply patch.
You are using a full package which is another situation.
If you have the full ota firmware downloaded from official website, you can try the follow steps
1.first make a nandroid backup of the old 5.1, make sure you can always restore your phone with backup
2.flash the official firmware zip with the twrp I attach( if any error occurred,do not reboot ,restore your phone with nandroid backup, also write down the error, and see which image file does not have the match SHA1, calculate and modify the sha1 of that line)
3.if step 2 succed ,do not reboot flash superSU zip file
4reboot, you may have superSU and your twrp may be replaced by stock recovery, use rashr flash twrp back again since you have root
Click to expand...
Click to collapse
update: the only issue i find is that SIM card isn't recognized
diosdetiempo said:
update: the only issue i find is that SIM card isn't recognized
Click to expand...
Click to collapse
sim card not recognized!? Sorry I can't really understand the reason of that because I don't have this problem.
Just a thought, maybe you lost baseband? Can you see your phone's IMEI number in settings? If you found null IMEI, that means you have lost your baseband, otherwise that's just something else maybe a small unknown issue, may also be the access point and protocol was not included in the 6.0 rom
If you lost your IMEI, I assume you already did the nandroid backup before, in twrp backup of NVRAM is the IMEI part, you should be able to recover your IMEI with that nvram backup
evilhawk00 said:
sim card not recognized!? Sorry I can't really understand the reason of that because I don't have this problem.
Just a thought, maybe you lost baseband? Can you see your phone's IMEI number in settings? If you found null IMEI, that means you have lost your baseband, otherwise that's just something else maybe a small unknown issue, may also be the access point and protocol was not included in the 6.0 rom
If you lost your IMEI, I assume you already did the nandroid backup before, in twrp backup of NVRAM is the IMEI part, you should be able to recover your IMEI with that nvram backup
Click to expand...
Click to collapse
have you tested with 6.0?
evilhawk00 said:
I made one and got root with A27 , all you need is a twrp and a twrp flashable firmware zip.
Here's what I did,first I found that the TWRP by @BouyaPK did not have the same device model settings in comparison with the stock recovery, so I made a little modification to his TWRP image, now the offical firmware zip can pass Device detection test.
!!Before doing it , make sure you have flashed the modified recovery(the one from attachment) to your phone, official firmware is only flashable via this modified recovery and stock recovery
Download here
View attachment 4137856
this is the example with the ota update package (A19 to A27 upgrade package around 150mb via coloros update manager app)
Now lets start to modify official firmware, follow my steps:
1.extract the newest official firmware zip.
2.now open the extracted folder, navigate to \META-INF\com\google\android\
3.find the file updater-script and open it with text editor( I suggest NotePad++)
4.you'll find a lot of lines start with apply_patch(xxxxx), remove the one with this file "/system/recovery-from-boot.p"
5.(if needed) also remove boot image sha1 check, in my case I have magisk installed, my boot image do not have the same sha1 value with stock boot image, so I found the line that checkes boot.img and remove it
6.done the file edit and save the file
7.repack it back to a zip file and sign the package with test keys
How to sign?
1.Download the sign package from attachment
2.have Java installed on your PC
3.Open a terminal at the same location with the keys and signapk.jar
4.terminal type
Code:
java -jar signapk.jar -w platform.x509.pem platform.pk8 my_modified_firmware.zip my_modified_firmware-signed.zip
8.install with twrp and you still have twrp exist, flash supersu zip or magisk zip
View attachment 4137905
above is the way to modify a PATCH zip ota file, if you are modifying a full package, which may be easier,
the full package's update script write full image to phone instead, so you just need to modify the image in the ota package.
all you just have to make sure the new firmware do not replace twrp with stock recovery, so
1.try to extract the image in the package and modify the image file, remove files such as "recovery-from-boot.p" from the image then rebuild the image and calculate the new sha1 value of the new image(CarlivImageKitchen is a good tool to rebuild image)
2.replace the old sha1 hash in updater-script, repack and sign the zip.
3.flash with twrp
4.flash superSu zip or magisk zip after the firmware flash with twrp can get root.
Click to expand...
Click to collapse
ok got it to work for a full firmware package here's what i did
1 . downloaded a27 (still 5.1 since 6.0 is not stable according to some)
2. using the twrp above flashed a27
3. flashed magisk
4. flash the twrp image again to make sure that incase it was overwritten by the update
NOTE: i did get an error like unable to mount dev/block/platform/...... it was fine for me
ngoralph said:
ok got it to work for a full firmware package here's what i did
1 . downloaded a27 (still 5.1 since 6.0 is not stable according to some)
2. using the twrp above flashed a27
3. flashed magisk
4. flash the twrp image again to make sure that incase it was overwritten by the update
NOTE: i did get an error like unable to mount dev/block/platform/...... it was fine for me
Click to expand...
Click to collapse
6.0 would work if the sim card issue could be fixed. i can't work it out :/
diosdetiempo said:
6.0 would work if the sim card issue could be fixed. i can't work it out :/
Click to expand...
Click to collapse
did you try restoring the nvram using twrp as stated before?
and did you wipe your data before flashing?? i think the transition from 5.1 to 6.0 may have broke some things read about it somewhere that wiping was necessary for LP to MM

[Help] LG G4 H815 LGUP failure

Hello!
I tried to update my Vodafone Branded G4 with the europe not branded version H81520g_00_0720.kdz
The problem ist i just get "error code = 0x2000, invalid command response" from the LGUP software and everytime i start the phone it is in firmware update mode.
Any idea how to fix this?
Greetings
I got this too as I tried to install H81520o_00_0310.kdz then I thought that it is maybe related to the brand. So I download your kdz file and then it was working.
So I would guess try another number is the best what you can do. I believe it is because of selection of "upgrade". If you have a tot file for refurbish, then maybe another is working, but I didn't do this yet.
Probably the problem is the DLL.
Extract the DLL from the KDZ (the one you want to flash) and replace it with the one you have in LGUP (path; C:/Program files/LG Electronics/LGUP/Model/8992).
the_naxhoo said:
Probably the problem is the DLL.
Extract the DLL from the KDZ (the one you want to flash) and replace it with the one you have in LGUP (path; C:/Program files/LG Electronics/LGUP/Model/8992).
Click to expand...
Click to collapse
i have the same problem2.
all the kdz that i download not come with any dll files just a 1.73 gb one file size.
kobisa25 said:
i have the same problem2.
all the kdz that i download not come with any dll files just a 1.73 gb one file size.
Click to expand...
Click to collapse
you must extract it from the KDZ with this tool: Click Here
the_naxhoo said:
you must extract it from the KDZ with this tool: Click Here
Click to expand...
Click to collapse
hi so i extract the kdz from LGExtract&7za& manuall tool& when i use winrar to extract its tell me no archive found i try also in winzip software. do you have any idea what else 2do?
thank you.
You can also try the codefire dll: http://downloads.codefi.re/autoprime/LG/LG_G4
( Download and rename LGFLASH_LG_G4_CODEFIRE.dll )
sfX
GOT IT!
the_naxhoo said:
you must extract it from the KDZ with this tool: Click Here
Click to expand...
Click to collapse
so after a long long search and dosents off error i succeeded
i find the currect kdz ISRAEL one and from it i EXTRACT it with WindowsLGFirmwareExtract-1.2.5.0-Release dll file and downgraded to lollipop 5.5 only with this dll file i make it after i try a few rom stocks that work with the dll.
i want to thank you you direct me to the right way:good:
Hi,
I have LG H811 (T-Mobile) Variant. I receive error from LGUP everytime I try to flash this ROM=h81120x_00_1108.kdz
My LGUP shows COM =COM3 and Version=H81120v
The error is thrown at 9%
Nothing working for me I am very frustrated!!!
PLEASE SOMEBODY HELP ME!
Stuck with LG G4 (H81520i)
Same for me but with LG H81520i. I tried to flash these ROM* with their specific .dll that I extracted thanks to WindowsLGFirmwareExtract-1.2.5.0-Release. Always get "error code = 0x2000, invalid command response" from LGUP. The error is thrown at 16% on the computer, but at 7% on the phone. Now, I'm stuck in download mode. I also tried to change the COM port number, doesn't change anything.
*Europe General H81510B_00.kdz ; Europe OPEN H81510D.kdz ; H81510D_00.kdz ; H81520i_00_0922.kdz ; SEA H81510B.kdz
Only one ROM above matches the LG H81520i (the fourth one).
Informations about my (ex-)android firmware :
- Android version : 6.0 (Marshmallow)
- Kernel version : 3.10.84
- Software version : V20-SEA-XX
PS : H81520i is what is written on the LGUP software
______________________________________________________________________________
I found a solution (after several hours)
Uninstall all your LG softwares (except LG Bridge or others LG backup softwares) and go to 'C:\Program Files (x86)\LG Electronics\' to delete all folders and files.
Go to this link and click on "Download all". Extract the file and follow the instructions :
1) Install "LGMobileSupportTool.exe"
2) Install "LGMobileDriver_WHQL_Ver_4.2.0.exe"
3) Install "LGUP_Install_Ver_1_14_3.msi"
4) Install "LGUP_8994_DLL_Ver_0_0_3_23.msi"
5) Move "LGUP_8994.dll" in the repertory 'C:\Program Files (x86)\LG Electronics\LGUP\model\8994'
6) Open "LGMobile Support Tool" and click on "Install USB driver." to the left
7) Select "LGH815" (or your model) et follow the drivers installation steps
8) Do step 5) again
9) Shut off your LG and plug it to your computer while pressing volume up in order to enter download mode
10) Unplug your LG and the battery
11) Open "LGUP" and close it
12) Do step 9 again (download mode)
13) Open "LGUP", select "UPGRADE" and go select your .kdz file (the ones in the file that you downloaded or another one you have)
14) Click on "Start" and DON'T TOUCH !!!!!!
Big thanks to the people of this reddit post and of this XDA thread
See above
Back To Stock ROM LG G4 H811 (T-Mobile)
LucasDupanne said:
________________________________________________________
First of all, I'm not allowed to post links as a new user , so I put them with spaces that you must delete :laugh: . Good luck !
Uninstall ALL your softwares (except LG Bridge or others LG backup softwares) and go to 'C:\Program Files (x86)\LG Electronics\' to delete all folders and files.
Go to this link ( ht tps : / / ya di . sk /d / KIG5F8 2jmXcUR ) and click on "Download all". After downloading the file, extract it and follow the instructions :
1) Install "LGMobileSupportTool.exe"
2) Install "LGMobileDriver_WHQL_Ver_4.2.0.exe"
3) Install "LGUP_Install_Ver_1_14_3.msi"
4) Install "LGUP_8994_DLL_Ver_0_0_3_23.msi"
5) Move "LGUP_8994.dll" in the repertory 'C:\Program Files (x86)\LG Electronics\LGUP\model\8994'
6) Open "LGMobile Support Tool" and click on "Install USB driver." to the left
7) Select "LGH815" et follow the drivers installation steps
8) Do step 5) again
9) Shut off your LG and plug it to your computer while pressing volume up in order to enter download mode
10) Unplug your LG and the battery
11) Open "LGUP" and shut it
12) Do again step 8 (download mode)
13) Open "LGUP", select "UPGRADE" and go select your .kdz file (your one or the ones in the file that you downloaded)
14) Click on "Start" and DON'T TOUCH !!!!!!
==>> thanks to ' ht tps : / / www .reddit . com /r/lgg4/comments/7anayg/downgraded_from_n_to_mm_and_stuck_in_download / ' post
A french man of 15 years that thanks Lobster_Johnson123 very very much.
PS : Sorry, my english is bad And let me know !!! :fingers-crossed:
Click to expand...
Click to collapse
Thanks Lucas for your time and help. It didn't work for me. I flashed another ROM named H811V20r_00_0111.kdz and it worked like a charm and it's tested on so many devices afterwards which worked fine without a single issue.
Here is the link to the ROM: https://lg-roms.com/official-firmware/LG G4-LGH811VK/H811V20r_00_0111/
Thanks for the help though.
androhead said:
Thanks Lucas for your time and help. It didn't work for me. I flashed another ROM named H811V20r_00_0111.kdz and it worked like a charm and it's tested on so many devices afterwards which worked fine without a single issue.
Here is the link to the ROM:
Thanks for the help though.
Click to expand...
Click to collapse
Happy it worked an other way for you !
i had working H815 version 29A nougat installed but for some reason
( nougat restarting issue ) during flashing H815 version 10d , after 9 percent same error comes , i tried by copying extracted dll from H815 v10d kdz in the LGUP (8994 folder) but nothing works for me,
please friends come to resolve my issue. waiting for reply from xda experts
Sanaullahshuaib said:
i had working H815 version 29A nougat installed but for some reason
( nougat restarting issue ) during flashing H815 version 10d , after 9 percent same error comes , i tried by copying extracted dll from H815 v10d kdz in the LGUP (8994 folder) but nothing works for me,
please friends come to resolve my issue. waiting for reply from xda experts
Click to expand...
Click to collapse
You need H81520p.kdz to downgrade from Nougat!
You can download from here: https://www.4shared.com/file/hfyqh6iEfi/H81520p_00_0314.html
Can also see here if you need more files: https://forum.xda-developers.com/showpost.php?p=76571471&postcount=23
Okay I'll try this but please tell me that
I have to copy lgup_8994.dll from H81520p or use original dll which is installed with the LGUP 8994 installer???
Sanaullahshuaib said:
Okay I'll try this but please tell me that
I have to copy lgup_8994.dll from H81520p or use original dll which is installed with the LGUP 8994 installer???
Click to expand...
Click to collapse
After install everything, replace the one in "C:\Program Files (x86)\LG Electronics\LGUP\model\8994" by the given one (or extract from the H81520p.kdz file).
See on the picture how your phone should be detected in "Device Manager":
http://i1376.photobucket.com/albums/ah39/RuedasLocas/Varios/Sem Tiacutetulo_zpsrrscdqov.jpg
H815v20p flashed correctly but mobile in boot-loop then i back installed H815v10d the original but also restarting
xda experts???
whats the issue in your mind experts XDA???
Sanaullahshuaib said:
H815v20p flashed correctly but mobile in boot-loop then i back installed H815v10d the original but also restarting
xda experts???
whats the issue in your mind experts XDA???
Click to expand...
Click to collapse
You first start your phone with any sim or sd card?
Try to flash it again with the v20p and restart it without any card on it.
If it doesn't solve the problem, try a v10a. Maybe it works and you can upgrade starting from there.
Good luck!
now again I tried H815v29A so it installed after the installation of old original version , now please tell the method of rooting Nougat on H815v29A urgently XDA experts???
also Twrp not installing on H815v29A which was working on marshmallow/////
experts reply???

I need help!

all i want is a Xiaomi A2 Lite 9.6.4.0 STOCK FIRMWARE OR ROM
but instead i'm getting all these zip files that has single file named Xiaomi A2 Lite build number android number etc or files like payload.bin i don't know how to use them, and i can't flash it thru Mi Flash Tool it gives me some red error
can i please get a stock OTA for 9.6.4.0 for my A2 lite that works with MiFlash Tool
Thanks
Essaxoxo said:
all i want is a Xiaomi A2 Lite 9.6.4.0 STOCK FIRMWARE OR ROM
but instead i'm getting all these zip files that has single file named Xiaomi A2 Lite build number android number etc or files like payload.bin i don't know how to use them, and i can't flash it thru Mi Flash Tool it gives me some red error
can i please get a stock OTA for 9.6.4.0 for my A2 lite that works with MiFlash Tool
Thanks
Click to expand...
Click to collapse
http://en.miui.com/download-354.html
pdue said:
http://en.miui.com/download-354.html
Click to expand...
Click to collapse
I've tried it it's not working, It's giving me an error, as well it has only one big file under zip and when I extract it on my desktop and place it inside a folder MiFlash tool doesn't flashes it
Essaxoxo said:
I've tried it it's not working, It's giving me an error
Click to expand...
Click to collapse
also I want to flash OTA of 9.6.4.0
First, it is nobody's fault but your own that you are where you are.
No user here owes you anything, you take the risk when attempting to mod your device.
Demanding help usually won't benefit you.
The following is the only official rom available from xiaomi at the moment.
pdue said:
http://en.miui.com/download-354.html
Click to expand...
Click to collapse
If you want the earlier versions you will need to locate the file yourself.
As for your error in miflash, it sounds to me as if you haven't unzipped the file correctly.
When you unzip, what is in the folder?
If it's another archived file, unzip again.
You should end up with an uncompressed folder with several commands and a folder full of images.
That should get you through miflash.
Here is a pic of files you should see for miflash to work
I have made a video - no sound
https://youtu.be/hvnYE1PuM7w

REQUEST Could someone upload oeminfo for EVR-L29 C432 EMUI 9?

-edit-no solution yet
Attempting to find an answer from users-does anyone have a bootloader unlocked (and rooted) EVR-L29 with cust C432 region? Could you please install and run partitions backup and recovery app (Play store) and upload your oeminfo.img?
Thanks so much! (this file is not available in the dload file-after many attempts (managed to find the partition layout and was able to dissect the dload into individual images but no oeminfo) It might be in some other full firmware format but I do not know of one. It can be readily extracted from a rooted phone though.
Thanks.

Categories

Resources