Hello,
I recently uninstalled some (system / T-Mobile) apps with Titanium Backup. And I did not make a backup first. The phone still runs fine but the OTA fails.
I tried so far:
- RUU 1.28 -> does not work, because system is already 1.29
- find rom.zip and unpack -> Ok, but cannot unpack system.img, unyafs fails.
The file which the OTA misses, according to logfile is named: 4661_TMODE_Music_One.odex
If someone could sent me this file or upload it somewhere I would be thankful.
There is a good chance that there are more files missing, but the log stops after the first fail.
I see in the system.img that there are at least 4 files with similar names:
4661_TMODE_Music_One.odex
4661_TMODE_Music_One.apk
4662_TMDE_Games_One.odex
4662_TMDE_Games_One.apk
If anyone knows how to unpack these, this would also helpful.
deleted
I think the best way to get all your bloatware back is to lock the bootloader and then flash the 129 RUU. Here is the link for the RUU if its T-mobile uk.
http://www.filefactory.com/file/6y1...Radio_1.1204.105.14_release_260731_signed.exe
Once your back to stock you can unlock again with your unlock token, flash cwm and make a stock nandroid backup.
If you need a file factory password pm me.
No, it's T-Mobile Germany, so I guess this will not help.
At the moment I'm trying to unpack the files from the system.img, but none of the methods described in the forums are working.
It is almost crazy, I can see the filenames and contents (lots of "PK" headers for instance) within the system.img but I've no idea how to extract them.
Get in touch with football. He might be able to get the RUU for you.
ghori1989 said:
Get in touch with football. He might be able to get the RUU for you.
Click to expand...
Click to collapse
Ok, tried that, waiting for the reply.
Meanwhile I'm able to mount the system image with some modifications as ext4 image and copy the contents. If there is an interest for this, I propably could write some tool to make this automatic.
Anyway, it did not help me, because the versions of the files in the image do not match the ones expected from the OTA.
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
Hello Guys,
i opened the thread in the Question&Answer Forum but somehow i have an different approach now that i learned how to rollback an firmware version with an locked bootloader. i dont know if it is possible, i more want to open like a discussion about it if this would be an thing someone could possibly do (and thats the reason im opening another thread for it, since it is not the same question anymore as in the other thread).
well, you can flash an image like EML-L29 8.1.0.129 to the device via the dload method. this image installs just fine, great. but now.. in my understanding the interesting part is this update.app. this update.app as far as my knowledge goes contains all this img files. you know, kernel system boot recovery etc.. wouldnt it be possible to simply replace the recovery.img with an twrp recovery.img, put the update.app back together, zip it in the necessary update_sdcard file and try to install it? i read about the tool "HuaweiUpdateExtractor", and this handy nice tool is showing the files.
another thought of me is: the installer is *verifying* the update.app somehow. but if it is verifying this file, there must be like a crc-file, some way of telling "this file is original" or "this file is okay". so maybe this is another part of the problem that i would have to take care of. but still i would need to know a lot more about the way the eRecovery works.
my ultimate goal is to solve the bootloader code problem since tackling it with dc-unlock and hcu wont work cause the security patch level seems already too high in the first versions of this phone. im basically search now ways around it - i know, there is actually no way to do it, but this is the reason why im opening this thread in hope to get some clues or ideas - and telling my own. oh and im pretty sorry if this is maybe annoying, i surely dont have any intention of spam the forums or stress too much on this topic (but it got me very interested).
Edit: i read in another board that it is nearly Impossible to switch the img files because they are encrypted. I guess it is not possible with this method so basically.. just ignore this thread. I guess there is really no way.
Also I think they have to do some checksum when flashing, so it's really impossible to just switch files...
About dload, i'm on 9.0.0.293 on EML-L29C432
I try the dload method to rollback to android 8.1, no success
i use an usb otg, created dload folder to root and place update.app extracted zip in dload folder
Also i created an "EML-L29_hw_eu" folder inside dload with again extracted from the hw zip file
When i use the dialer method, phone recognize the update.app file and reboot
after reboot to recovery, i have an error and i can't downgrade
What i did wrong ?
thanks
bender8125 said:
About dload, i'm on 9.0.0.293 on EML-L29C432
I try the dload method to rollback to android 8.1, no success
i use an usb otg, created dload folder to root and place update.app extracted zip in dload folder
Also i created an "EML-L29_hw_eu" folder inside dload with again extracted from the hw zip file
When i use the dialer method, phone recognize the update.app file and reboot
after reboot to recovery, i have an error and i can't downgrade
What i did wrong ?
thanks
Click to expand...
Click to collapse
well the biggest problem may be the image itself that you are trying to flash. if you take it from firmwarefinder, you will get most likely absolutely no success. you need to take one from androidhost.ru, the ones there worked for me. there you just put everything in the dload folder on your USB-Stick. oh and better use an full-OTA, not just an simple ota update, because that wont work (you cant just update a few files when you are already on EMUI 9). and on top of that: backup your phone first, because it is possible that after your downgrade you lose all data on your phone.
oh and another thing if you just want to get back to EMUI 8.1 (not a specific version you wish for), just use hisuite, because they are allowing the downgrade even more easily. the method i mentioned above is if you try to flash a specific version like i did with 8.1.0.120
Hey, Ive been out of the scene for a long time. Lately due to OP's poor software, I've been wanting to run a custom rom. I have a Chinese LE2120 crossflashed to global and was wondering if 1) its okay to downgrade using the Global MSM tool. and 2) how I can do a complete backup of my phone. For reference, on my OP8 I lost the ability to use the fingerprint sensor after restoring my device. luckily OP fixed it for free but im not sure theyd be so kind with a chinese variant that I got on ebay. I was thinking I need to at least back up my modem and whatever partition the fingerprint sensor calibration is on. What else should I back up and how should I do it? Im not rooted currently.
You can find full firmware of all partition in your phones ssd. Go to this website https://onepluscommunityserver.com/list/Unbrick_Tools/ and select your phone model and version. Download file. After download finished unpack zip and delete all file without the ops file. You can use this tool to decrypt ops file and extract partitions from it. https://github.com/bkerler/oppo_decrypt
After you have decrypted.
In your extract folder, will you get many non partition file. You can open settings.xml and see who file is partition, on program tags.