I flashed Xperience Rom on my OPX after taking a full TWRP backing and wiping /data and /system after that.
After that I have No IMEI, so no SIM ; No WiFi connectivity and unknown baseband as shown in screenshot.
I have already tried,
- Full reset
- Flashing OOS 3.1.4.
- Flashing OOS 2.2.2.
- Restoring backup.
Nothing is helping. What should I do?
Try flashing new baseband from here:
https://forum.xda-developers.com/oneplus-x/general/zip-recovery-flashable-firmware-radio-t3381420
If it won't help, maybe this will help:
https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Caraparbor said:
Try flashing new baseband from here:
https://forum.xda-developers.com/oneplus-x/general/zip-recovery-flashable-firmware-radio-t3381420
If it won't help, maybe this will help:
https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Click to expand...
Click to collapse
Tried them all, nothing is happening. I locked my bootloader by flashing that baseband; qualcomm tools saved me.
Thanks anyways
How did you fix this? I think I have the same problem.
Related
Hello, I'm new member in here. Today I flashed UltimaROM to my SGS3. Before the flashing I installed Philz touch recovery and saved Nandroid, modem and EFS backups in my PC. After the flashing no IMEI number was shown and I got a message saying " Insert SIM card....". So i tried to restore EFS in custom restore option in philz recovery. Even though it showed restore successful , IMEI number is still unavailable and i couldn't connect to mobile network. I also tried ktools to restore efs but no result. Can someone please help me regarding this issue.
What version firmware did you have before you first flashed? If it was really old then that could be the problem.
Flash a 4.3 stock rom, factory reset them boot and see if your efs is read again.
boomboomer said:
What version firmware did you have before you first flashed? If it was really old then that could be the problem.
Flash a 4.3 stock rom, factory reset them boot and see if your efs is read again.
Click to expand...
Click to collapse
Thanks for the reply. I had 4.1.2. If I flash 4.3 stock ROM can i retrieve my IMEI ?
If you flash a 4.3 stock it will update your efs to v2 and should enable it to be read in all newer firmwares.
I tried unlocking my bootloader unofficially and bricked it, then trying to fix it I may have accidentally wiped all my partitions.
Luckily I followed the guide and unbricked it via the 'teardown' method, flashed V7.2.3.0.LHOCNDA with MI flash and it is now up and running again.
The issue now is I cannot turn on Wi-Fi and the phone cannot detect my sim card. Baseband is unknown and i have no iemi.
I have flashed several different versions and it is still the same.
I am now rooted and have twrp recovery
Could wiping all the partitions do this, is it reversible?
BTW: it a 16gb Pro from china if that helps
Danvman said:
I tried unlocking my bootloader unofficially and bricked it, then trying to fix it I may have accidentally wiped all my partitions.
Luckily I followed the guide and unbricked it via the 'teardown' method, flashed V7.2.3.0.LHOCNDA with MI flash and it is now up and running again.
The issue now is I cannot turn on Wi-Fi and the phone cannot detect my sim card. Baseband is unknown and i have no iemi.
I have flashed several different versions and it is still the same.
I am now rooted and have twrp recovery
Could wiping all the partitions do this, is it reversible?
BTW: it a 16gb Pro from china if that helps
Click to expand...
Click to collapse
If u had previously backed up efs then restore it, if not then head over to miui.en forum there is a tutorial on how to restore imei no.
Hello,
After a fail flash custom rom, my phone got bricked. Somehow, i recovered it.
But now, i'm facing two major issues : No IMEI, No BaseBand (Wi-Fi is still working.)
I've tried every single post concerning : Restoring Imei and Restoring EFS partition.
(When i tried to restore the EFS partition following this guide : https://forum.xda-developers.com/redmi-note-3/how-to/flash-recover-efs-snapdragon-t3406789 . It requested me a password after booting)
Please help me, it'll save my life :crying:
Hamdiz said:
Hello,
After a fail flash custom rom, my phone got bricked. Somehow, i recovered it.
But now, i'm facing two major issues : No IMEI, No BaseBand (Wi-Fi is still working.)
I've tried every single post concerning : Restoring Imei and Restoring EFS partition.
(When i tried to restore the EFS partition following this guide : https://forum.xda-developers.com/redmi-note-3/how-to/flash-recover-efs-snapdragon-t3406789 . It requested me a password after booting)
Please help me, it'll save my life :crying:
Click to expand...
Click to collapse
Update to the latest developer preview rom and then try the efs tricks and also try to be calm don't worry..
Hey guys,
I have a problem with my Galaxy S III I9300. I have been using a CM 13 rom for some months now, which has worked perfectly fine untli yeserday.
My Phone crashed randomly, which happens sometimes, but after this crash it was stuck in bootloop. I tried to reboot, no result.
After restoring a backup it worked for some time until it suddenly crashed and stucked in bootloop again. Same with factory reset.
I have even flashed a new rom ArchiDroid , via CWM, with the same result.
I hope you guys can help me out with this problem.
Thank you in advance,
GeneralD
Have you tried flashing the latest stock ROM with Odin, performing a factory reset from stock recovery, and then using the phone for a while to verify functionality?
audit13 said:
Have you tried flashing the latest stock ROM with Odin, performing a factory reset from stock recovery, and then using the phone for a while to verify functionality?
Click to expand...
Click to collapse
Definitely. Flash to stock should be the first thing you do if your phone goes into bootloop.
OK, I flashed the stock rom & recovery and did a factory reset. Until now everything is working fine, except the "Not registered on network" Error, which I have now
Any solution?
Does the phone show the correct imei? Have you tried manually searching and connecting to a network?
audit13 said:
Does the phone show the correct imei? Have you tried manually searching and connecting to a network?
Click to expand...
Click to collapse
Wrong Imei...
Does it start work 0049..? Do you have a backup of the efs folder? You flashed the latest stock rom?
I have an efs backup of a now destroyed s3.. can it be used for anything like reviving efs borked s3's?
Im sorry guys,
I flashed a old 4.1 stock rom, found the latest 4.3 rom now and the Error is gone
But wont I be able to flash custom roms from now on?
GeneralD said:
Im sorry guys,
I flashed a old 4.1 stock rom, found the latest 4.3 rom now and the Error is gone
But wont I be able to flash custom roms from now on?
Click to expand...
Click to collapse
If all you did was flash a stock rom you should be ok to do what you like to it.
Hello! I tried to install the newest official OTA update while being on v10 (rooted with Magisk). It rebooted to TWRP and I tried to install the OTA manually in TWRP. Schouldn't have done this... this is where all the problems started. I was afraid I bricked my phone for a few hours, but finally I managed to get it back up. I'm now running the newest official OTA update.
Unfortunately, wifi and bluetooth isn't working. Mobile data (LTE) is working fine. Everything else works just fine. Does anyone here have any idea what the problem can be? If I remember correctly, wifi and bluetooth problems are often due to modem or firmware problems? Or maybe a problem with boot.img or vbmeta.img? I've messed with vbmeta.img and because I have full root with Magisk my boot.img is also modified. Thanks a lot for your help!
Edit: some additional info:
Build number: DN2103_11_A.11
Smallbandversion: M_V3_P10,M_V3_P10
Kernel-version: 4.14.186+
If I go to about phone -> status it shows no bluetooth address and no mac-address for wifi.
characterdivide said:
Hello! I tried to install the newest official OTA update while being on v10 (rooted with Magisk). It rebooted to TWRP and I tried to install the OTA manually in TWRP. Schouldn't have done this... this is where all the problems started. I was afraid I bricked my phone for a few hours, but finally I managed to get it back up. I'm now running the newest official OTA update.
Unfortunately, wifi and bluetooth isn't working. Mobile data (LTE) is working fine. Everything else works just fine. Does anyone here have any idea what the problem can be? If I remember correctly, wifi and bluetooth problems are often due to modem or firmware problems? Or maybe a problem with boot.img or vbmeta.img? I've messed with vbmeta.img and because I have full root with Magisk my boot.img is also modified. Thanks a lot for your help!
Edit: some additional info:
Build number: DN2103_11_A.11
Smallbandversion: M_V3_P10,M_V3_P10
Kernel-version: 4.14.186+
If I go to about phone -> status it shows no bluetooth address and no mac-address for wifi.
Click to expand...
Click to collapse
I you have backup of efs partation of just restore that via twrp
Unfortunately I don't think so. I made a backup but without EFS partition. Is there anything else I could try?
characterdivide said:
Unfortunately I don't think so. I made a backup but without EFS partition. Is there anything else I could try
Click to expand...
Click to collapse
Oneplus Nord 2 Oxygen 11.3 DN2103 EEA ROM
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process! Downloads: The Fastboot restoration file can be downloaded in here: DN2103_11_A.07 DN2103_11_A.10 *deleted DN2103_11_A.11 *deleted...
forum.xda-developers.com
Try to flash this
Thanks, I will try that! Should I flash the complete rom? Or only one of the update parts (for example V10 to V11 update)?
characterdivide said:
Thanks, I will try that! Should I flash the complete rom? Or only one of the update parts (for example V10 to V11 update)?
Click to expand...
Click to collapse
Yes
characterdivide said:
Hello! I tried to install the newest official OTA update while being on v10 (rooted with Magisk). It rebooted to TWRP and I tried to install the OTA manually in TWRP. Schouldn't have done this... this is where all the problems started. I was afraid I bricked my phone for a few hours, but finally I managed to get it back up. I'm now running the newest official OTA update.
Unfortunately, wifi and bluetooth isn't working. Mobile data (LTE) is working fine. Everything else works just fine. Does anyone here have any idea what the problem can be? If I remember correctly, wifi and bluetooth problems are often due to modem or firmware problems? Or maybe a problem with boot.img or vbmeta.img? I've messed with vbmeta.img and because I have full root with Magisk my boot.img is also modified. Thanks a lot for your help!
Edit: some additional info:
Build number: DN2103_11_A.11
Smallbandversion: M_V3_P10,M_V3_P10
Kernel-version: 4.14.186+
If I go to about phone -> status it shows no bluetooth address and no mac-address for wifi.
Click to expand...
Click to collapse
Can you tell me what happened actually while updating? Did you successfully flashed new update in twrp or some else
Okay, I try to write everything down that I still remember. Frist, I tried to install latest official OTA on my rooted phone. It tried to restart into recovery, where I manually installed the official OTA package. After that, my phone didn't boot. It was stuck on the oneplus boot animation. I tried to restore a backup I made of the stock rom V10. After that, I don't remember exactly what I did, but I think I flashed the vmbeta.img from the 'how to root oneplus nord 2' guide. I also tried wiping cache, data, etc. multiple times. After another time of trying to restore an old backup + formatting the whole phone it booted and seemed to work fine. Until I discovered that bluetooth and wifi weren't working...
So
characterdivide said:
Okay, I try to write everything down that I still remember. Frist, I tried to install latest official OTA on my rooted phone. It tried to restart into recovery, where I manually installed the official OTA package. After that, my phone didn't boot. It was stuck on the oneplus boot animation. I tried to restore a backup I made of the stock rom V10. After that, I don't remember exactly what I did, but I think I flashed the vmbeta.img from the 'how to root oneplus nord 2' guide. I also tried wiping cache, data, etc. multiple times. After another time of trying to restore an old backup + formatting the whole phone it booted and seemed to work fine. Until I discovered that bluetooth and wifi weren't working...
Click to expand...
Click to collapse
Someone told me that after downloading incremental update package ROM Boots to twrp but failed to flash update and nothing happened he booted to old OS
Yes, that's right, after auto reboot nothing happened in TWRP, but I manually navigated to the .zip file of the OTA update and installed it in TWRP. For me this worked and the OTA succesfully installed. But I think this didn't work as it should because my phone was rooted using Magisk. Maybe it has something to do with the fact that my boot.img was patched by Magisk? And installing the OTA over that would cause problems?
characterdivide said:
Yes, that's right, after auto reboot nothing happened in TWRP, but I manually navigated to the .zip file of the OTA update and installed it in TWRP. For me this worked and the OTA succesfully installed. But I think this didn't work as it should because my phone was rooted using Magisk. Maybe it has something to do with the fact that my boot.img was patched by Magisk? And installing the OTA over that would cause problems?
Click to expand...
Click to collapse
So you have to flash old roms boot.img it will. Help to back everything
Thanks a lot! It worked, I'm so relieved!
For anyone else who broke their phone this way: flash V10 stock image -> flash V10 to V11 update .zip -> flash vbmeta.img. Boot phone and it's fixed.
characterdivide said:
Thanks a lot! It worked, I'm so relieved!
For anyone else who broke their phone this way: flash V10 stock image -> flash V10 to V11 update .zip -> flash vbmeta.img. Boot phone and it's fixed.
Click to expand...
Click to collapse
Give me V10 stock image FOR DN 2101
And after flashing this will our TWRP avilable or Not agian?
Done
characterdivide said:
Thanks a lot! It worked, I'm so relieved!
For anyone else who broke their phone this way: flash V10 stock image -> flash V10 to V11 update .zip -> flash vbmeta.img. Boot phone and it's fixed.
Click to expand...
Click to collapse
Im having same issues as you could help me out what image did you use and how. Thanks in advance.