Related
As the title suggests, I'm wondering if flashing Honor 7x firmware over my Mate SE would do more harm than good, considering they're (almost) the same devices. Only asking because there's no firmware for the Mate SE to be found and I'm really desperate to get mine out of a bootloop. Unless someone has a clean dump that I can use?
There’s no firmware for the US 7X either
wisdomzw said:
There’s no firmware for the US 7X either
Click to expand...
Click to collapse
i know this is far fetched but can you make a twrp full backup because I accidentally deleted my firmware off my phone and a bunch of other people did also. I can't like use my phone or anything. Thanks
Check this out
tomjfmu said:
i know this is far fetched but can you make a twrp full backup because I accidentally deleted my firmware off my phone and a bunch of other people did also. I can't like use my phone or anything. Thanks
Click to expand...
Click to collapse
The Huawei Mate se and honor 7x usa came out.
http://pro-teammt.ru/firmware-database/?firmware_model=BND-L34&firmware_page=0
tomjfmu said:
i know this is far fetched but can you make a twrp full backup because I accidentally deleted my firmware off my phone and a bunch of other people did also. I can't like use my phone or anything. Thanks
Click to expand...
Click to collapse
Hey, did you manage to get a fix?
wisdomzw said:
Hey, did you manage to get a fix?
Click to expand...
Click to collapse
A new BND-L34 update came out. I tried extracting the update, and unfortunately I can't access my phone from adb anymore for some reason.
Huawei doesn't post their ADB drivers anywhere. The only way is from Hi suite, but you need stock ROM installed in order to access it to get the drivers.
Is there any way to get drivers?
First of all, i started being a newbie, i just wanted to install magisk for cam2api, but i messed up: i combined for error 2 different system (mine that was ios9 and ios8). So i tried to read more and more threads and it just got worse. to make the story short: i had to get to test-point and restore the phone with Xiaomi Mi Flash tool & an original rom stock.
So now that i can go inside the Android System and use the phone, my sim card is just not working, i checked and my imei was 0 and my IMEI SV also 0.
I tried deleting modemst 1 and 2, i tried to reflash the phone with another stock images, updating the phone via android (normal way), i tried to restore my imei with the QPST Dual Imei (and it worked but the IMEI SV still in 0). nothing is working Please i need help i think my efs folder it's corrupted but i'm not shure.
Also i don't have any EFS backup or System backup, nothing.
JoiaDG said:
First of all, i started being a newbie, i just wanted to install magisk for cam2api, but i messed up: i combined for error 2 different system (mine that was ios9 and ios8). So i tried to read more and more threads and it just got worse. to make the story short: i had to get to test-point and restore the phone with Xiaomi Mi Flash tool & an original rom stock.
So now that i can go inside the Android System and use the phone, my sim card is just not working, i checked and my imei was 0 and my IMEI SV also 0.
I tried deleting modemst 1 and 2, i tried to reflash the phone with another stock images, updating the phone via android (normal way), i tried to restore my imei with the QPST Dual Imei (and it worked but the IMEI SV still in 0). nothing is working Please i need help i think my efs folder it's corrupted but i'm not shure.
Also i don't have any EFS backup or System backup, nothing.
Click to expand...
Click to collapse
I´m not sure what you mean by ios8 and ios9, maybe oreo and pie.
For the next time just so you know test point method is not recommended while you are not completely bricked (although is recommended out there without care), on a unlocked device most probably you won´t need it to solve this kind of issue, there are other resources to try previous to this stage.
I never had this kind of problem, you might try this https://zfirmware.com/how-to-repair-qualcomm-imei-via-qualcomm-write-imei-tool/
Sadly not working
SubwayChamp said:
I´m not sure what you mean by ios8 and ios9, maybe oreo and pie.
For the next time just so you know test point method is not recommended while you are not completely bricked (although is recommended out there without care), on a unlocked device most probably you won´t need it to solve this kind of issue, there are other resources to try previous to this stage.
I never had this kind of problem, you might try this
Click to expand...
Click to collapse
Sadly, it didn't work. i was thinking if there was a way to do it with root
JoiaDG said:
Sadly, it didn't work. i was thinking if there was a way to do it with root
Click to expand...
Click to collapse
Try rewriting the IMEI's from the box (I hope you still have the box and paperwork since there is the original IMEI's) with the Qualcomm IMEI Tool. Reflash full stock rom.
The tool is here: https://androidmtk.com/download-qualcomm-smartphone-write-imei-tool
If everything fails and your knowledge is not helping you to find a solution and you are still under warranty and respect the warranty for physical aspect of the device (no scuffs, no damage, no aftermarket replaced parts that may damaged warranty voids inside the phone) you can flash it stock, lock bootloader and file a warranty replacement as "damage from OTA". The service will replace your motherboard.
I need help
TheoXSD said:
Try rewriting the IMEI's from the box (I hope you still have the box and paperwork since there is the original IMEI's) with the Qualcomm IMEI Tool. Reflash full stock rom.
The tool is here:
If everything fails and your knowledge is not helping you to find a solution and you are still under warranty and respect the warranty for physical aspect of the device (no scuffs, no damage, no aftermarket replaced parts that may damaged warranty voids inside the phone) you can flash it stock, lock bootloader and file a warranty replacement as "damage from OTA". The service will replace your motherboard.
Click to expand...
Click to collapse
I know i have to use that tool, but my device is not recognized by that app, i tried to install all the drivers, but nothing's working.
JoiaDG said:
Sadly, it didn't work. i was thinking if there was a way to do it with root
Click to expand...
Click to collapse
I knew that there is a method to restore IMEIs via adb but I don´t remember commands so I never need it. First I do before tinkering device is to backup IMEI/EFS/NVram.
I had a theory that years ago I proved, IMEI is not really lost but just overlapped so if you have some friend that can give you their backup this will recover the yours but won´t overwrite/replace the yours. Not sure if it works yet.
About the tool that I linked maybe you need to get it through either in fastboot or download mode, try both; I don´t think that detect it while device is on.
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161 i fixed the phone with this tutorial
JoiaDG said:
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161 i fixed the phone with this tutorial
Click to expand...
Click to collapse
Yeah this fixed my phone too, now I'm making backups
IMPORTANT NOTE TO USERS UPGRADING TO AN ANDROID 10 ROM:
Please BACKUP YOUR PERSIST PARTITION IN RECOVERY BEFORE FLASHING AN ANDROID 10 ROM, otherwise your device may be messed up seriously. Please read this post before upgrading to A10.
Update on this issue:
https://forum.xda-developers.com/ma...n-fixing-persist-issues-t4024247/post81656725
Apparently, due to the changes made by Google, some hacks needed to be done to make Q work with our device. Due to this, when installing an Android 10 ROM and other things like Magisk on it, some modifications are made to the persist partition. These changes might break some important stuff like Camera, Wifi, Torch etc for users who go back to Pie ROMs. Even when switching between TEN Roms, similar problems have come to some users.
*******************************************
****** WAYS TO BACKUP PERSIST ******
*******************************************
1) Using persist backup option in recovery
-> This option is present in recent versions of TWRP and other TWRP based recoveries. Its a good practice to always backup all the important partitions like Persist, EFS and Modem. These contain the most important stuff like IMEI, Wifi Mac address etc. which are unique to your device.
2) Making an Image backup of persist via recovery terminal
-> If the persist backup option isn't available, you can use the dd command from a terminal app (needs root rights) or from the recovery terminal.
Usage:
To create a backup and place it at /sdcard/persist.img:
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
To restore a backup which is placed at /sdcard/persist.img:
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
Thanks to @NZedPred, due to which I came across these commands. These appear to work universally and work on our device as well. Please be careful while typing the commands, especially while restoring the persist.img. Even a small mistake could be fatal for the device.
*************************************
********* FIXING PERSIST *********
*************************************
There is no guaranteed way to fix your broken ORIGINAL persist, but currently the only way to fix the broken stuff on your device is using someone else's persist. We need to obtain a twrp backup of the persist or persist.img from some other user who has not upgraded to Android 10.
Before fixing your persist, make a BACKUP of your ORIGINAL PERSIST even if it is broken. It contains important stuff UNIQUE to your device. It might be very helpful, in case someone discovers a fix to it in the future.
Please BEWARE, there are RISKS associated with using someone else's persist. Historically in other devices, it has been used to store IMEI and other important things.
But the following things are CONFIRMED TO BREAK if using someone else's persist.
1) WIDEVINE WILL BE PERMANENTLY STUCK AT L3, since the drm certificates unique to your device will be lost forever.
2) Persist stores your serial number as well, so your ORIGINAL SERIAL number may get lost when switching to stock.
***************************************
****** FIXING SERIAL NUMBER ******
***************************************
Fortunately there is a way to fix your serial number. In the root of your persist, there is a hidden file ".sn.bin". Opening it in a text editor, we can see the last 15 digits of the serial number of the other person's device, whose persist you have used. Copy and keep this number somewhere. Then follow below steps:
1) Backup the current persist.img using the above dd commands.
2) Open the persist.img using a hex editor. You can use any hex editor software for windows/linux or Hex Editor app from Play Store.
3) In the search option, set it to find strings. Set it to 'String' or something similar depending on your software.
4) Search for the 15 digit serial number which you found previously in .sn.bin file.
5) After you find it, replace or edit it to your original serial number. Make sure that you modify ONLY THOSE 15 DIGITS AND NOTHING ELSE.
6) Then save the modified persist.img
7) Restore the modified persist.img using dd commands as above.
8) Almost done, but the new changes in persist won't be detected by the system. So you will have to install the stock pie ROM. Relocking the bootloader is not required as per my testing. So follow the steps to install stock. Use OFRP and decrypt.zip as necessary, to deal with encryption.
9) Now boot up the device.
And voila. Go to settings and check your serial. It should be restored. You can now return to your custom ROM if you want. The serial number will be retained.
Same thing happened with my device too. Widevine security level is stuck at L3.
Although I'm back in the Official Stock ROM!
(locked bootloader)
Apolle said:
Same thing happened with my device too. Widevine security level is stuck at L3.
Although I'm back in the Official Stock ROM!
(locked bootloader)
Click to expand...
Click to collapse
Yes... Even after flashing stock firmware, widevine remains L3.
Some people have suggested me to install the last stock Oreo first and then install Stock Pie.
Maybe the Oreo firmware contains the original persist files...
The Oreo firmwares were around 1.6 to 1.8 GB, whereas the pie firmwares are around 1.5 GB.
So maybe they are right then...
Maybe if its possible for some of you to do this, you could try this...
I also messed up my persist partition. even i'm getting back to all stock (including recovery and locked bootloader) my phone can't recieve update, neither install updates manually. Also, my device is shown in playstore setting as "Device not certified". I'm still searching for a fix for this.
---------- Post added at 06:23 PM ---------- Previous post was at 06:21 PM ----------
Tyakrish said:
Yes... Even after flashing stock firmware, widevine remains L3.
Some people have suggested me to install the last stock Oreo first and then install Stock Pie.
Maybe the Oreo firmware contains the original persist files...
The Oreo firmwares were around 1.6 to 1.8 GB, whereas the pie firmwares are around 1.5 GB.
So maybe they are right then...
Maybe if its possible for some of you to do this, you could try this...
Click to expand...
Click to collapse
I also tried to install Oreo but, I can't update it to android Pie. It always failed.
kayamokid said:
I also tried to install Oreo but, I can't update it to android Pie. It always failed.
Click to expand...
Click to collapse
Could you tell which Oreo firmware ? If its very first Oreo firmware released by Asus, then you might need to update to the last available Oreo firmware and then upgrade to pie...
The last Oreo firmware I believe, prepares the device for pie...
So Pie might get installed after that
Tyakrish said:
Could you tell which Oreo firmware ? If its very first Oreo firmware released by Asus, then you might need to update to the last available Oreo firmware and then upgrade to pie...
The last Oreo firmware I believe, prepares the device for pie...
So Pie might get installed after that
Click to expand...
Click to collapse
If you haven't tried yet, try the persist.img from here & let us know if fix the problem.
Tyakrish said:
Could you tell which Oreo firmware ? If its very first Oreo firmware released by Asus, then you might need to update to the last available Oreo firmware and then upgrade to pie...
The last Oreo firmware I believe, prepares the device for pie...
So Pie might get installed after that
Click to expand...
Click to collapse
Oh, not the first one. i used .192 but no success... i hope there's a fix for this.. i miss stock rom so much...
mauam said:
If you haven't tried yet, try the persist.img from here & let us know if fix the problem.
Click to expand...
Click to collapse
I looked at this persist.img. But it appears weird to me. Just have a look at the contents of my persist image and this one.
Seems like a lot of stuff is missing...
Tyakrish said:
I looked at this persist.img. But it appears weird to me. Just have a look at the contents of my persist image and this one.
Seems like a lot of stuff is missing...
Is this supposed to be in a different format ? How can this be flashed ?
Click to expand...
Click to collapse
Let's see if @Wahyu6070 can enlighten us. His nick is wahyu hidayat on telegram if you want to reach him.
@kubersharma, I have spoken to many people about this issue and no one seems to know much about why it happens and how this issue can be fixed.
Can you give an insight as to why this persist problem happens ?
To save time, I linked to first post of this thread:
https://forum.xda-developers.com/ma...n-fixing-persist-issues-t4024247/post81288631
After much research, I have come to the conclusion that widevine can't be fixed. Since the drm certificates unique to our device are forever lost when some other user's persist is used. The other user's persist may contain some widevine files, but they are unique to his device and won't work with our device.
Completely Agreed with you because what I did confirm that it cannot be fixed.
I flashed Oreo Firmware Raw (Initial Oreo Firmware 158) by Fastboot/adb method. Then Install every single incremental Update by built-in Updater. But unfortunately the Widevine security level remains L3.
Apolle said:
Completely Agreed with you because what I did confirm that it cannot be fixed.
I flashed Oreo Firmware Raw (Initial Oreo Firmware 158) by Fastboot/adb method. Then Install every single incremental Update by built-in Updater. But unfortunately the Widevine security level remains L3.
Click to expand...
Click to collapse
Thanks for all that effort. I also tried with a fastboot firmware posted on 4pda. But no use.
Tyakrish said:
@kubersharma, I have spoken to many people about this issue and no one seems to know much about why it happens and how this issue can be fixed.
Can you give an insight as to why this persist problem happens ?
To save time, I linked to first post of this thread:
https://forum.xda-developers.com/ma...n-fixing-persist-issues-t4024247/post81288631
Click to expand...
Click to collapse
Try pm @wahyu6071 telegram
UPDATES:
- Added a way to make persist image backups (Can be useful for flashing persist.img files).
Check the first post
Apolle said:
Same thing happened with my device too. Widevine security level is stuck at L3.
Although I'm back in the Official Stock ROM!
(locked bootloader)
Click to expand...
Click to collapse
have you used other user's persist? are you able to install OTA after you made this process? i also use other's persist. and my imei is lost. and also, i cant update thru FOTA and manual method. it gives me an error in stock recovery.
kayamokid said:
i also use other's persist. and my imei is lost.
Click to expand...
Click to collapse
Wait a min. Did you lose your imei also ? I thought u only lost widevine L1 ?
Tyakrish said:
Wait a min. Did you lose your imei also ? I thought u only lost widevine L1 ?
Click to expand...
Click to collapse
yes. but i manage to restore it again, by editing .sn,bin file inside of persist folder. terrible happens when this persist problem occurs. i cant install or update stock rom manually. i hope there's a way to fix this. I miss clean, locked and unrooted stock rom.
kayamokid said:
yes. but i manage to restore it again, by editing .sn,bin file inside of persist folder. terrible happens when this persist problem occurs. i cant install or update stock rom manually. i hope there's a way to fix this. I miss clean, locked and unrooted stock rom.
Click to expand...
Click to collapse
You must be talking about Serial number. The file, .sn.bin contains the serial number. I don't think imei is lost if we use someone else's persist. I didn't lose mine and I came across many other people, they also didn't lose imei.
Based on what you are saying, I think serial number gets lost as well along with widevine...
Because even I lost my serial number after installing stock pie via fastboot
Deleted
A while back when the 6 Pro was released, I ended up with a bootloop and lost my imei in the process of recovering the phone. Long story short, was wondering if anyone has or can make a QCN backup for the Red Magic 6 Pro, preferably on the current firmware for NA/Asia and change the coded imeis/meids in the backed up .qcn file to default numbers like 1234...etc so any personal info is taken out?
For policy reasons, I can't explain how to change any of that though.
There you go.
adwinp said:
There you go.
Click to expand...
Click to collapse
Thanks boss, giving things a last ditch effort before I toss it in the recycle pile. Wish me luck lmao
Edit: I finally got to take a look at the file and is this for a Red Magic 6 Pro?
It seems to be from an altogether different model of device, encoded specs are for a generic Qualcomm Snapdragon 835 model, the RM6P has a Snapdragon 888.
Tried using it anyways for the hell of it after backing up the existing efs, my IMEIs were both listed but I lost all SIM card detection. Went to restore the last QCN and my IMEIs were missing but I had SIM card detection.
Seem to be unable to get the IMEIs to stick to my existing backup, shows as NULL.
adwinp said:
There you go.
Click to expand...
Click to collapse
hey..
can u pls share xqcn.. after this file still i have the network problem..
wbr..
I have a OnePlus 9 Pro. Lost my dual sim function after updating to Android 13 in a weird way (it was ok at first). Now it shows only one. I want to revert to the European LE2123 as saw it can support it. I am in Hong Kong and seems this is the best option as I don't need the India version and I don't necessarily need Chinese (at least I don't read Chinese).
I have searched and gone down too many rabbit holes- so hope someone has been there already and can guide me.
Thanks!
David
XDAdaveHK said:
I have a OnePlus 9 Pro. Lost my dual sim function after updating to Android 13 in a weird way (it was ok at first). Now it shows only one. I want to revert to the European LE2123 as saw it can support it. I am in Hong Kong and seems this is the best option as I don't need the India version and I don't necessarily need Chinese (at least I don't read Chinese).
I have searched and gone down too many rabbit holes- so hope someone has been there already and can guide me.
Thanks!
David
Click to expand...
Click to collapse
Your phone model ?
XDAdaveHK said:
I have a OnePlus 9 Pro. Lost my dual sim function after updating to Android 13 in a weird way (it was ok at first). Now it shows only one. I want to revert to the European LE2123 as saw it can support it. I am in Hong Kong and seems this is the best option as I don't need the India version and I don't necessarily need Chinese (at least I don't read Chinese).
I have searched and gone down too many rabbit holes- so hope someone has been there already and can guide me.
Thanks!
David
Click to expand...
Click to collapse
To revert your OnePlus 9 Pro to the European version of Android 13 (LE2123), you will need to flash the firmware for that version onto your device. This is a technical process that involves using specialized software to replace the operating system on your device.
Before you begin, you should make sure that you have backed up all of your important data, as the process will erase everything on your device. You will also need to download the firmware for the European version of Android 13 (LE2123) and the appropriate flashing tool.
To flash the firmware onto your device, you will need to follow these steps:
Enable developer mode on your device by going to Settings > About phone > Software information > More > Developer options.
Enable USB debugging on your device by going to Settings > Developer options > USB debugging.
Connect your device to your computer using a USB cable.
Open the flashing tool and follow the prompts to install the firmware onto your device.
When the process is complete, your device will restart and you should be able to use the European version of Android 13 (LE2123).
It is important to note that this process can be risky and may result in data loss or damage to your device if not done correctly. If you are not comfortable with technical processes or are unsure about how to proceed, it is recommended that you seek the assistance of a professional.
ElitePotato said:
Your phone model ?
Click to expand...
Click to collapse
Oneplus 9 Pro. LE2125. But I read somewhere that the LE2125 can be changed to LE2123 with the software change as it is not hardware-dependent entirely. Yes, the Indian hardware version has different radio frequencies, but the EU and US are very similar. Anyway- I have gone down a rabbit hole and not really sure.
XDAdaveHK said:
Oneplus 9 Pro. LE2125. But I read somewhere that the LE2125 can be changed to LE2123 with the software change as it is not hardware-dependent entirely. Yes, the Indian hardware version has different radio frequencies, but the EU and US are very similar. Anyway- I have gone down a rabbit hole and not really sure.
Click to expand...
Click to collapse
Use LE2125 msmtool and then flash the LE2123 OOS11 rom through fastboot. It can be done by payload flasher also, payload file is included in full rom zip. Once you have converted to LE2123, do a factory reset and you can update it normally all the way to OOS13.
.
.
Read the op9 guide if you are confused.
ChristianMorris said:
To revert your OnePlus 9 Pro to the European version of Android 13 (LE2123), you will need to flash the firmware for that version onto your device. This is a technical process that involves using specialized software to replace the operating system on your device.
Before you begin, you should make sure that you have backed up all of your important data, as the process will erase everything on your device. You will also need to download the firmware for the European version of Android 13 (LE2123) and the appropriate flashing tool.
To flash the firmware onto your device, you will need to follow these steps:
Enable developer mode on your device by going to Settings > About phone > Software information > More > Developer options.
Enable USB debugging on your device by going to Settings > Developer options > USB debugging.
Connect your device to your computer using a USB cable.
Open the flashing tool and follow the prompts to install the firmware onto your device.
When the process is complete, your device will restart and you should be able to use the European version of Android 13 (LE2123).
It is important to note that this process can be risky and may result in data loss or damage to your device if not done correctly. If you are not comfortable with technical processes or are unsure about how to proceed, it is recommended that you seek the assistance of a professional.
Click to expand...
Click to collapse
Thank you- thank you for being professional to provide assistance. I can do the flash but wanted to make sure it was safe/possible before I tried. Currently, the phone is not working well enough to keep it as is, so worth any risk to fix it. Currently using a Xiaomi 11T Pro and love it- so I know there is a huge gap in getting the OnePlus working properly again.
But where is the 'flashing tool' found?
XDAdaveHK said:
Thank you- thank you for being professional to provide assistance. I can do the flash but wanted to make sure it was safe/possible before I tried. Currently, the phone is not working well enough to keep it as is, so worth any risk to fix it. Currently using a Xiaomi 11T Pro and love it- so I know there is a huge gap in getting the OnePlus working properly again.
But where is the 'flashing tool' found?
Click to expand...
Click to collapse
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com