Hi Everyone,
I have an issue when I flash any ROM (except MIUI8) on my 6503 the ROM flashes fine, and system loads up fine, but when I click anywhere and the system wants to play the touch sound, it reboots. If I connect a USB digital headset to the phone, issue does not occur.
I also tried flashing the 6502 fix, which interestingly solves this issue for all the ROMs, but if i do this, the SIM card is not being detected.
So, what I am doing -
downgraded my phone to 4.4.4 with Flashtool
installed CWM via fastboot
wiped completely
---
also tried with TWRP flashed by other ROMs, issue is the same.
So I just don't really know what to do, or what do i do wrong, hope you can help, please.
Thank you.
danieel said:
Hi Everyone,
I have an issue when I flash any ROM (except MIUI8) on my 6503 the ROM flashes fine, and system loads up fine, but when I click anywhere and the system wants to play the touch sound, it reboots. If I connect a USB digital headset to the phone, issue does not occur.
I also tried flashing the 6502 fix, which interestingly solves this issue for all the ROMs, but if i do this, the SIM card is not being detected.
So, what I am doing -
downgraded my phone to 4.4.4 with Flashtool
installed CWM via fastboot
wiped completely
---
also tried with TWRP flashed by other ROMs, issue is the same.
So I just don't really know what to do, or what do i do wrong, hope you can help, please.
Thank you.
Click to expand...
Click to collapse
flash bootloop fix from here : https://mega.nz/#!AJcwERiQ!FUmk6eS5aoVsFSZ1f4WZIELIt7sckPCj11n0AIdCNzU
Related
Hello guys,
as a last resort I turn to you for help. Have been searching for the answer for the last 2 days. I am running CWM-based Recovery v.6.0.1.1 and have a rooted x10 together with an unlocked bootloader. I flashed the recovery without any problems and installed miui v4 but an older file which was very unstable (without any problems). Then I decided to install the newer version so i downloaded it, placed it on my sdcard and in the same recovery flashed rom. Unfortunately I had my usb cable plugged in all the time (during installation). Installation got stuck in the middle and nothing could be done so i removed the battery and started the phone again (this time without the usb cable). When I tried to reinstall that rom again it gave me status 7 error installation aborted, assert failed:getprop,error in sdcard and things like that. So I tried the ROM which had already worked on my phone but received exactly the same message. What is more usb storage mounting in the recovery doesnt work anymore (but it already worked!). Now the problem is that I don't have any system installed and when i try to flash the recovery again, flashtool does not recognize my phone (so does windows) and so it leads me nowhere. I think this is definitely problem with the recovery, after the failed attempt to install rom when i had to remove the battery it does not behave normally. Is there any way that I can maybe install another recovery from .zip - i do not even know whether it will install or just sends me another error. Any help would be greatly appreciated
SqU33z3R said:
Hello guys,
as a last resort I turn to you for help. Have been searching for the answer for the last 2 days. I am running CWM-based Recovery v.6.0.1.1 and have a rooted x10 together with an unlocked bootloader. I flashed the recovery without any problems and installed miui v4 but an older file which was very unstable (without any problems). Then I decided to install the newer version so i downloaded it, placed it on my sdcard and in the same recovery flashed rom. Unfortunately I had my usb cable plugged in all the time (during installation). Installation got stuck in the middle and nothing could be done so i removed the battery and started the phone again (this time without the usb cable). When I tried to reinstall that rom again it gave me status 7 error installation aborted, assert failed:getprop,error in sdcard and things like that. So I tried the ROM which had already worked on my phone but received exactly the same message. What is more usb storage mounting in the recovery doesnt work anymore (but it already worked!). Now the problem is that I don't have any system installed and when i try to flash the recovery again, flashtool does not recognize my phone (so does windows) and so it leads me nowhere. I think this is definitely problem with the recovery, after the failed attempt to install rom when i had to remove the battery it does not behave normally. Is there any way that I can maybe install another recovery from .zip - i do not even know whether it will install or just sends me another error. Any help would be greatly appreciated
Click to expand...
Click to collapse
Flash tool recognize your phone? if yes flash any stock firmware and start over
quintas84 said:
Flash tool recognize your phone? if yes flash any stock firmware and start over
Click to expand...
Click to collapse
When I want to flash .tft file and i go to flash mode it does not recognize my phone in windows even though I have installed all the necessary drivers. It starts to flash but then says flashing aborted (this did not happen before, i could flash without any problems). Another problem is that i do not have any rom installed right now so i cannot even switch debugging on and if i remember right, i left debugging off in my previous rom.
Use Sony Update Service. Download from Sony site and install on PC. Follow the instruction, and this will reflash Stock Rom and Kernel (GB 2.3.3). Then, with latest Flashtool, first Root phone again, then flash whatever you want (custom kernels, roms..). You don't need to unlock bootloader again. It remains unlocked.
Sent from my X10i using xda premium
Dzufa said:
Use Sony Update Service. Download from Sony site and install on PC. Follow the instruction, and this will reflash Stock Rom and Kernel (GB 2.3.3). Then, with latest Flashtool, first Root phone again, then flash whatever you want (custom kernels, roms..). You don't need to unlock bootloader again. It remains unlocked.
Sent from my X10i using xda premium
Click to expand...
Click to collapse
Omg - I found solution to my problem - I just changed usb port and it started to flash even using flashtool. Still, many thanks since it helped me find solution
So I think I may have messed up my firmware. I odin'd it with a shady tar and ever since then my recovery randomly reboots when I choose zips to install. My Bluetooth isn't working, it won't even enable. I flashed the stock tar from sammobile and then rooted that,now im running cm10.1. Bluetooth is the only thing that hasn't worked yet but has anyone else had this issue?
Bluetooth issues is a known bug with 4.2 and 4.1 based roms.
Yeah but those are issues with the sound and how lo the volume is. i fixed the bluetooth issue by going into recovery and wiping cache/dalvik and re-installing 10.1 then fixing permissions which i figured it might but i added that info just in case. I re-installed my recovery from goomanager app and im still having issues with it which i hope isn't contributed to firmware.
rangercaptain said:
Bluetooth issues is a known bug with 4.2 and 4.1 based roms.
Click to expand...
Click to collapse
Issues can mean 100's of things.
Be specific.
you are seeing random reboots in the firmware ? Or when you access Recovery ?
RR's in the 4.2 firmware are expected, as we use an uber-modified ICS kernel to run JB.
If recovery is causing a reboot condition, you have a dirty recovery partition, or the recovery image itself is damaged. Either way, a new recovery file should be flashed to test. And I suggest TWRP, directly from the TWRP site. Note: Version 2.4.2.0 caused a recovery reboot condition for me. I reverted to 2.4.1.0 and the condition went away.
Good luck Sir.....g
Yeah I tried the flashing of a new recovery from twerp site and that's when the issue started. Also, if you read the list and comments you would have seen the exact Bluetooth issue and the issue I thought may be my firmware. If you had the same issue with tarp 2.4.2 than it must be that and not the firmware because I wiped all possible partitions and reinstalled everything from scratch the other day.
gregsarg said:
Issues can mean 100's of things.
Be specific.
you are seeing random reboots in the firmware ? Or when you access Recovery ?
RR's in the 4.2 firmware are expected, as we use an uber-modified ICS kernel to run JB.
If recovery is causing a reboot condition, you have a dirty recovery partition, or the recovery image itself is damaged. Either way, a new recovery file should be flashed to test. And I suggest TWRP, directly from the TWRP site. Note: Version 2.4.2.0 caused a recovery reboot condition for me. I reverted to 2.4.1.0 and the condition went away.
Good luck Sir.....g
Click to expand...
Click to collapse
Update
I went to twrp site today and downloaded and installed twrp 2.4.3 and it fixed the random recovery reboots but when the screen shuts off i cant bring it back up, it just stays black. Im not sure if its still installing the ROM or what but i just hold down the button and reboot into recovery again. I have to constantly move my finger around the screen to keep it awake.
Atrix2destroyer said:
Yeah I tried the flashing of a new recovery from twerp site and that's when the issue started. Also, if you read the list and comments you would have seen the exact Bluetooth issue and the issue I thought may be my firmware. If you had the same issue with tarp 2.4.2 than it must be that and not the firmware because I wiped all possible partitions and reinstalled everything from scratch the other day.
Click to expand...
Click to collapse
Yes, I saw your issues....as you stated a bluetooth error....(ROM related, not recovery).
I also saw your recovery issue, and said to flash TWRP 2.4.1.0...
Then you flashed 2.4.3.0 and are still having issues. Did you flash 2.4.1.0 ?? because if you did, your recovery issues would be gone.
And if you flash a ROM with known bluetooth issues like CM 10.1, then you will have bluetooth issues.....g
I accidentally wiped system and other partitions from my nx529j.
i was trying to flash stock rom but in stock recovery it says SD card not detected.
Even in TWRP i was unable to flash stock rom (Both 5.1.1 and 6.0.1). Custom ROM is installed but during calls neither me nor the other person can hear each others voice.
Internet is working fine.
Help.
I have the same problem. When I flashed RR or Mokee rom I was unable to hear call sound. I searched many forums but nothing helped. So i decided to flash stock rom bac, but it stuck on "Be yourself" or something like that. Now I am usim RR rom but without phone function which is very weird. Have anyone the same issue?
The same problem
Pauliesss said:
I have the same problem. When I flashed RR or Mokee rom I was unable to hear call sound. I searched many forums but nothing helped. So i decided to flash stock rom bac, but it stuck on "Be yourself" or something like that. Now I am usim RR rom but without phone function which is very weird. Have anyone the same issue?
Click to expand...
Click to collapse
I have similar problem. I have some Lineage 7.1 ROM and I want to flash back Stock ROM 6.0 beta, but I just try flash rom from official support page (.zip) and via TWRP and it show me ERROR I think, that maybe it isnt flashable file, but I dont know, how to change it to.
Please HELP US!!
Redminote 4 SD have gone to boot loop after a custom rom ,after that i used different methods like fastboot miui rom and .zip miui rom nothing seems to work can anybody have a solution?(device strats and after boot into mui for one min and restrats itself) most of the cutom roms has been used nothing have a soluition?
teja.asodi said:
Redminote 4 SD have gone to boot loop after a custom rom ,after that i used different methods like fastboot miui rom and .zip miui rom nothing seems to work can anybody have a solution?(device strats and after boot into mui for one min and restrats itself) most of the cutom roms has been used nothing have a soluition?
Click to expand...
Click to collapse
If you were able to boot into TWRP, reboot to recovery > wipe everything > flash this firmware : https://androidfilehost.com/?fid=889964283620754602, next flash any custom rom (download any rom from development section), flash Gapps > reboot! Lemme know how it goes. Good luck.
Not worked...problem remains same
Just download Lazy Flasher .Zip file. and install it via twrp after flashing custom rom .
Your problem will solve for sure.
same happens for me since yesterday. I was using a custom rom since some time and without changing anything after reboot I am running into the same trouble.
Have tried to reinstall official miui rom, lock bootloader etc.
I am afraid this might be a hardware failure.
Hi,
was able to fix my note 4. Have installed twrp 3.1.1-8.0 on my second note 4 and created a backup of all partitions to sd card. Then I have adjusted the serial number of the stored backup to match the one of the broken note 4. After restoring the whole device with the backup files from the working device the reboots are gone.
But it seems like now IMEI, MAC address and Bluetooth address are invalid and/or not correct. Was able to fix at least IMEI.
Have not identified any further issues so far.
BTW: from inside twrp recovery the phone never rebooted.
it seems to be a problem with firmware without firmware the device will boot fine but there wont be bt, fp , calling, sound, wifi etc.
but with firmware it will just bootloop.
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.