Related
Updated my new x522 to 5.8.021s now I have no phone or data. It sees the sim and my phone number on the sim but it won't go on the network. Everything else is fine so have 2 questions.
1. Can and how can I flash a new modem to the 5.8.021s firmware?
2. What modem should I use I am in California on T-mobile?
Baseband MPSS TA 2.1 c700008-8976 GEN PACK-1.85233.30.76286.2
EUI version 5.8.021S
Thanks in advance.
Rick
dainbramage said:
Bought this phone last week off ebay thought I would update the firmware so I found the 5.8.021s file and did the update ZIP. It updated fine and everything worked except the phone. It shows the sim card as t-mobile with my phone number and cellular data calls and messages as t-mobile but when I try search for network I get "error searching for network". I tried different sims that I know are good and nothing works. I would return it to the original firmware but I wasn't smart enough to back it up. I would flash a new modem if I knew how maybe that is the problem. I have an x829 as my daily driver this was going to be a birthday gift.
Baseband MPSS TA 2.1 c700008-8976 GEN PACK-1.85233.30.76286.2
EUI version 5.8.021S
Thanks in advance.
Rick
Click to expand...
Click to collapse
Seems like you flash a wrong ROM that is meant for different country.
Download EUI stock official ROM which is meant for your country then flash it with chinese twrp once you flash it
Fixed it. Installed the small EUI by aurel. He had a note about my predicament on the first page. Great ROM for me and a big thank you to him. So here is what I did. Probably would have worked on the 21s too.
1. Download the adb, fastboot drivers
2. Install it on your PC.
3. Restart the phone in fastboot mode (power + vol down)
4. Type this commands in the terminal:
Quote:
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
5. Done.
Thanks again
I got this problem fixed after using fastboot erase persist, and fastboot flash persist /directory/persist.img.
I Got stocked after trying used fastboot erase (each of my partitions) and well not remember what more i did. Just tried installing a lot of stock custom rooms (that not worked) and also remember that the twrp keeping said not able to mount persist partition.
Hello everyone, two days ago I flashed Android P on my Moto G6 (Stock ROM) after moving off of a custom ROM, I forgot to test call audio. Today, I got several phone calls, and there is NO call audio. Does anyone have any idea how to fix this?
NolanLinuxDev said:
Hello everyone, two days ago I flashed Android P on my Moto G6 (Stock ROM) after moving off of a custom ROM, I forgot to test call audio. Today, I got several phone calls, and there is NO call audio. Does anyone have any idea how to fix this?
Click to expand...
Click to collapse
Must flash the NON-HLOS.bin file from a 8.0.0 firmware through adb fastboot mode over your PIE:
"fastboot flash modem NON-HLOS.bin"
HueyT said:
Must flash the NON-HLOS.bin file from a 8.0.0 firmware through adb fastboot mode over your PIE:
"fastboot flash modem NON-HLOS.bin"
Click to expand...
Click to collapse
Gonna try that now.
HueyT said:
Must flash the NON-HLOS.bin file from a 8.0.0 firmware through adb fastboot mode over your PIE:
"fastboot flash modem NON-HLOS.bin"
Click to expand...
Click to collapse
Flashed that file, and my phone started working again instantly! Thank you!
NolanLinuxDev said:
Flashed that file, and my phone started working again instantly! Thank you!
Click to expand...
Click to collapse
Yeah, sometimes Pie modem doesn't flash correctly on some phones
HueyT said:
Must flash the NON-HLOS.bin file from a 8.0.0 firmware through adb fastboot mode over your PIE:
"fastboot flash modem NON-HLOS.bin"
Click to expand...
Click to collapse
hey, i flashed that on android pie and i dont know why that did not work! please help me!! im on the last update ever to the moto g6 which is the april 1 security patch and i tried flashing the android 8 modem but it says sim card is not found, so please help me!!
NolanLinuxDev said:
Flashed that file, and my phone started working again instantly! Thank you!
Click to expand...
Click to collapse
hey can you please tell me what the file name is exactly?
My Redmi Note 3 Kenzo is bricked, it doesn't go past MI Logo.
I have tried flashing multiple stock ROMs in edl and fastboot mode, mi flash tool says success but device doesn't go past MI Logo.
This happened when I was trying to repair my lost IMEI, I found this thread on XDA:
https://forum.xda-developers.com/redmi-note-3/how-to/recover-redmi-note-3-sd-imei-baseband-t3744385
My device was bricked after I wrote the following commands:
fastboot flash modemst1 modemst1
fastboot flash modemst2 modemst2
fastboot flash fsg fsg
I can still access fastboot, please help.
Samip12 said:
My Redmi Note 3 Kenzo is bricked, it doesn't go past MI Logo.
I have tried flashing multiple stock ROMs in edl and fastboot mode, mi flash tool says success but device doesn't go past MI Logo.
This happened when I was trying to repair my lost IMEI, I found this thread on XDA:
https://forum.xda-developers.com/redmi-note-3/how-to/recover-redmi-note-3-sd-imei-baseband-t3744385
My device was bricked after I wrote the following commands:
fastboot flash modemst1 modemst1
fastboot flash modemst2 modemst2
fastboot flash fsg fsg
I can still access fastboot, please help.
Click to expand...
Click to collapse
THREE threads about the same issue AND in the wrong forum?
Samip12 said:
My Redmi Note 3 Kenzo is bricked, it doesn't go past MI Logo.
I have tried flashing multiple stock ROMs in edl and fastboot mode, mi flash tool says success but device doesn't go past MI Logo.
This happened when I was trying to repair my lost IMEI, I found this thread on XDA:
https://forum.xda-developers.com/redmi-note-3/how-to/recover-redmi-note-3-sd-imei-baseband-t3744385
My device was bricked after I wrote the following commands:
fastboot flash modemst1 modemst1
fastboot flash modemst2 modemst2
fastboot flash fsg fsg
I can still access fastboot, please help.
Click to expand...
Click to collapse
Are u sure phone is kenzo and not kate?
Many users lost thier baseband coz of flashing wrong miui rom on wrong device.
If above is not the cause then may be its due to replacing of duplicate incompatible parts. Never go to local unauthorized shops.
Black_Stark said:
Are u sure phone is kenzo and not kate?
Many users lost thier baseband coz of flashing wrong miui rom on wrong device.
If above is not the cause then may be its due to replacing of duplicate incompatible parts. Never go to local unauthorized shops.
Click to expand...
Click to collapse
oh ****, looks like its kate, the model number in my box is 2015161, https://forum.xda-developers.com/redmi-note-3/help/guys-how-tell-kate-kenzo-t3479255
i rememebr trying to flash a kate image and mi flash said mismatching image and device and i thought my device was kenzo.
What should I do now?
Samip12 said:
oh ****, looks like its kate, the model number in my box is 2015161, https://forum.xda-developers.com/redmi-note-3/help/guys-how-tell-kate-kenzo-t3479255
i rememebr trying to flash a kate image and mi flash said mismatching image and device and i thought my device was kenzo.
What should I do now?
Click to expand...
Click to collapse
I just flashed kate image in edl mode, but the device did not boot. I have found this new tool called mi flash pro, now i'm trying to flash via recovery .Previously, i had to enter my IMEI number as the fields were blank, but now my IMEI was already there. Looks like I have my IMEI in the device now but the device is not booting.
Samip12 said:
I just flashed kate image in edl mode, but the device did not boot. I have found this new tool called mi flash pro, now i'm trying to flash via recovery .Previously, i had to enter my IMEI number as the fields were blank, but now my IMEI was already there. Looks like I have my IMEI in the device now but the device is not booting.
Click to expand...
Click to collapse
Kate is redmi note 3 special edition. Its not written on box ?
Kenzo is 15.0 cm
Kate is 15.2 cm.
Black_Stark said:
Kate is redmi note 3 special edition. Its not written on box ?
Kenzo is 15.0 cm
Kate is 15.2 cm.
Click to expand...
Click to collapse
Its just written Redmi Note 3 in box.
Looks like it's 15cm, but .. 15 and 15.2, too close to be determined.
I had a similar issue in my friend's phone. Now you need to keep a few things in mind.
1) is the device rebooting back to mi logo again and again - the reason for this is a faulty battery.
2) is the device kenzo or kate??? Kenzo was sold in 2+16 and 3+32 configuration. Kindly check on the box for the network band support and compare with gsmarena.
3)you need to flash miui 7 rom if you need to recover your device. My volte was completely broken and that's the only way i could fix it.
Good luck
tejasvi001 said:
I had a similar issue in my friend's phone. Now you need to keep a few things in mind.
1) is the device rebooting back to mi logo again and again - the reason for this is a faulty battery.
2) is the device kenzo or kate??? Kenzo was sold in 2+16 and 3+32 configuration. Kindly check on the box for the network band support and compare with gsmarena.
3)you need to flash miui 7 rom if you need to recover your device. My volte was completely broken and that's the only way i could fix it.
Good luck
Click to expand...
Click to collapse
My device appears to be kate.
The mi logo doesn't reappear. It appears then the device turns off.
I'll try with MIUI 7.
tejasvi001 said:
I had a similar issue in my friend's phone. Now you need to keep a few things in mind.
1) is the device rebooting back to mi logo again and again - the reason for this is a faulty battery.
2) is the device kenzo or kate??? Kenzo was sold in 2+16 and 3+32 configuration. Kindly check on the box for the network band support and compare with gsmarena.
3)you need to flash miui 7 rom if you need to recover your device. My volte was completely broken and that's the only way i could fix it.
Good luck
Click to expand...
Click to collapse
flashed MIUI 7 ROM , device didn't boot as usual. The mi logo appears and the device shuts off itself.
What might be the problem?
Muhammad Haris
Your wrong in flash modemts1, modemts2, and fsg. So make your device stuck at mi logo. Not like that solution for write imei back to your device.
I give recommend, you try open cmd(minimal adb fastboot). You can search in google about minimal adb fastboot. And you type command like that:
Fastboot modemst1 erase
Fastboot modemst2 erase
Fastboot fsg erase
That's will make your phone lose imei. But your phone Will normal booting. To write imei, maybe I can help other time. Now, you must try it. Can or not to make your phone normal. Oke. Thank you
is it a faulty battery? I have been using this device since 2016 and the battery didn't last good the last time the device worked. I can boot into fastboot, I can boot into recovery, everytime I flash ROM it says success, I can flash and use TWRP. I can do everything except using the system. I just tried installing lineage OS 14.1. Sometimes after MI logo, the lineage OS animation appears a little bit and the device shuts off again.
Mharis0799 said:
Your wrong in flash modemts1, modemts2, and fsg. So make your device stuck at mi logo. Not like that solution for write imei back to your device.
I give recommend, you try open cmd(minimal adb fastboot). You can search in google about minimal adb fastboot. And you type command like that:
fastboot modemst1 erase
fastboot modemst2 erase
fastboot erase fsg
That's will make your phone lose imei. But your phone Will normal booting. To write imei, maybe I can help other time. Now, you must try it. Can or not to make your phone normal. Oke. Thank you
Click to expand...
Click to collapse
Thank you so muchh man , my phone is booting again I can't thank you enough mate.
Mharis0799 said:
Your wrong in flash modemts1, modemts2, and fsg. So make your device stuck at mi logo. Not like that solution for write imei back to your device.
I give recommend, you try open cmd(minimal adb fastboot). You can search in google about minimal adb fastboot. And you type command like that:
Fastboot modemst1 erase
Fastboot modemst2 erase
Fastboot fsg erase
That's will make your phone lose imei. But your phone Will normal booting. To write imei, maybe I can help other time. Now, you must try it. Can or not to make your phone normal. Oke. Thank you
Click to expand...
Click to collapse
I wrote the above command and flashed kate ROM through edl mode,now my device is booting and everything is working except sim card and loudspeaker. The IMEI is unknown.
Samip12 said:
I wrote the above command and flashed kate ROM through edl mode,now my device is booting and everything is working except sim card and loudspeaker. The IMEI is unknown.
Click to expand...
Click to collapse
I also remember flashing a kenzo persist.img file on my device, does that have anything to do with loudspeaker?
Black_Stark said:
Are u sure phone is kenzo and not kate?
Many users lost thier baseband coz of flashing wrong miui rom on wrong device.
If above is not the cause then may be its due to replacing of duplicate incompatible parts. Never go to local unauthorized shops.
Click to expand...
Click to collapse
if I'm not mistaken only the rom changes between kenzo and kate so this shouldn't be the problem.
---------- Post added at 10:40 AM ---------- Previous post was at 10:37 AM ----------
Samip12 said:
flashed MIUI 7 ROM , device didn't boot as usual. The mi logo appears and the device shuts off itself.
What might be the problem?
Click to expand...
Click to collapse
Try with flashing a custom rom via twrp, now android 6 is an outdated system.
MatteoGemma said:
if I'm not mistaken only the rom changes between kenzo and kate so this shouldn't be the problem.
---------- Post added at 10:40 AM ---------- Previous post was at 10:37 AM ----------
Try with flashing a custom rom via twrp, now android 6 is an outdated system.
Click to expand...
Click to collapse
my phone boots now, everything works except loudspeaker and SIM is not detected due to unknown IMEI, also tried lineage OS 14.1 same problem.
Samip12 said:
my phone boots now, everything works except loudspeaker and SIM is not detected due to unknown IMEI, also tried lineage OS 14.1 same problem.
Click to expand...
Click to collapse
Try with an android 9/10 official custom rom
Samip12 said:
I wrote the above command and flashed kate ROM through edl mode,now my device is booting and everything is working except sim card and loudspeaker. The IMEI is unknown.
Click to expand...
Click to collapse
With those commands, its already mentioned it will make you LOSE imei but help in booting... & That worked for you...
He then said to guide you how to write back imei. So you should now look for the procedure to restore imei infos., Or wait for him to tell you...
Recently, I reverted to stock oreo only to go back to PE again. Since then, I have been wondering if it's causing some of my issues. Camera quality with gcam isn't what it used to be, the network indicator in the status bar shows no bars but I can get and receive calls, random wakeup's while the phone is in my pocket and performance issues on my keyboard(sometimes I press the keys but there's no response).
What are your guys thoughts? Should I have had updated to latest version before going to PE?
BungeeWatcher47 said:
Recently, I reverted to stock oreo only to go back to PE again. Since then, I have been wondering if it's causing some of my issues. Camera quality with gcam isn't what it used to be, the network indicator in the status bar shows no bars but I can get and receive calls, random wakeup's while the phone is in my pocket and performance issues on my keyboard(sometimes I press the keys but there's no response).
What are your guys thoughts? Should I have had updated to latest version before going to PE?
Click to expand...
Click to collapse
if you go from oreo to 10 and back again you need to restore your persist partition or it will be corrupted and give you problems with everything from wifi to camera to compass
so either go to stock rom android 10 or restore your persist or go to Pe and stay there .. I've explained this to another guy like a day ago with links so just search for that post because I'm too lazy to repeat it again
KevMetal said:
if you go from oreo to 10 and back again you need to restore your persist partition or it will be corrupted and give you problems with everything from wifi to camera to compass
so either go to stock rom android 10 or restore your persist or go to Pe and stay there .. I've explained this to another guy like a day ago with links so just search for that post because I'm too lazy to repeat it again
Click to expand...
Click to collapse
I found your reply on the pixel experience forum, page 48. From there, I have flashed persidtgood.zip file using sky hawk recovery. After, I rebooted thrice. My camera and WiFi have seen some improvement but not my sim network. Anyway, do you think I should flash the latest PE now or go back to stock android 10 using edl mode and then go back to PE May 24 update..
BungeeWatcher47 said:
I found your reply on the pixel experience forum, page 48. From there, I have flashed persidtgood.zip file using sky hawk recovery. After, I rebooted thrice. My camera and WiFi have seen some improvement but not my sim network. Anyway, do you think I should flash the latest PE now or go back to stock android 10 using edl mode and then go back to PE May 24 update..
Click to expand...
Click to collapse
return to stock with edl mode if everything is not 100% but if everything is working well now you can proceed with any custom rom
KevMetal said:
return to stock with edl mode if everything is not 100% but if everything is working well now you can proceed with any custom rom
Click to expand...
Click to collapse
I will go back to stock just to make sure that the network issues are not from my side.. How do you actually flash from edl? I have tried searching for it but I couldn't find anything substantial..
Do I use fastboot reboot edl on fastboot screen and proceed to flash with Mi flash tool? But I remember you mentioning that Mi flash isn't very good since it doesn't flash important partitions..
BungeeWatcher47 said:
I will go back to stock just to make sure that the network issues are not from my side.. How do you actually flash from edl? I have tried searching for it but I couldn't find anything substantial..
Do I use fastboot reboot edl on fastboot screen and proceed to flash with Mi flash tool? But I remember you mentioning that Mi flash isn't very good since it doesn't flash important partitions..
Click to expand...
Click to collapse
use cmd:
fastboot oem edl
then :
use miflash and select unzipped stock fastboot rom and select the "clear all" option in the box at the bottom
THEN :
fastboot boot recovery.img
THEN :
custom recovery should boot on phone without installing ...then restore/ flash persist img or persist zip
Reboot & Enjoy fully functioning phone
I have a Chinese Oneplus 10 Pro which I received with ColorOS 12.1 Android 12 NE2210_11_A_07. It then updated OTA with ColourOS 13 .x but the Google Assistant ("Hey Google!") functionality was not working. So then I tried to flash a global rom to fix the problem.
Using this guide: https://forum.xda-developers.com/t/...-gl-in-without-rooting.4430017/#post-86729081
I tried to flash a number of different payload files but nothing is working.
I have tried the following ROMS, in order:
OxygenOS 13.0 С.22 GLOBAL
OxygenOS 13.0 С.22 EU
OxygenOS 13.0 С.22 India(IN) (NE2211_11.C.22)
Oxygen OS 12.1 A11 EU
Oxygen OS 12.1 A11 IND
Color OS 12.1 A.15f
ColorOS 13.0.0 Open Beta C.16
OnePlus 10 Pro Rollback Package EU
I also flashed 2x stock Boot.img files in an attempt to help the situation but that also did not work. I got a "qualcom crashdump mode" error then.
As title says I am still stuck in bootloop. Nothing I have tried can fix this.
What I have noticed recently is that the fastbootd value in "Fastboot Enhance v1.4" said "no" even after I restarted it in Fastbootd mode.
I tried to run fastboot reboot fastboot command and now the device is completely dead. Does not switch on anymore at all and no response when charging.
What have I done wrong? And is it possible I bricked my device?
yup. your device is bricked. only msm tool can help you in this case which i available with oneplus service centers only
doomisunderlove said:
yup. your device is bricked. only msm tool can help you in this case which i available with oneplus service centers only
Click to expand...
Click to collapse
Thanks, I was able to unbrick it with the help of a forum member who used the MSM tool for 20USD.
Follow - up question, why did it brick?
Is it not possible to flash another ROM on this device?
Nokoff said:
Thanks, I was able to unbrick it with the help of a forum member who used the MSM tool for 20USD.
Follow - up question, why did it brick?
Is it not possible to flash another ROM on this device?
Click to expand...
Click to collapse
You might have corrupted a partition on the device while trying to flash packages one after another. You probably put the icing on the cake after flashing only boot.img instead of a clean flash once again (could have saved your partition) forcing your device into qualcom crash dump mode. As much as I understand msm tool it allows one to unbrick your device directly on the soc level while reformatting the partitions.
It's not like you cannot flash other roms on this devices but developer tend to avoid oneplus now because if a brick like this happens they are forced to rush to service center to get it unbricked. Since oneplus never release their msm tool to the general public. So yeah, I believe this is it for oneplus until good people at xda find a way.
Also, flashing a rom twice will confirm the fact that the rom is on both the partitions since different part of the phone use different partitions.
doomisunderlove said:
You might have corrupted a partition on the device while trying to flash packages one after another. You probably put the icing on the cake after flashing only boot.img instead of a clean flash once again (could have saved your partition) forcing your device into qualcom crash dump mode. As much as I understand msm tool it allows one to unbrick your device directly on the soc level while reformatting the partitions.
It's not like you cannot flash other roms on this devices but developer tend to avoid oneplus now because if a brick like this happens they are forced to rush to service center to get it unbricked. Since oneplus never release their msm tool to the general public. So yeah, I believe this is it for oneplus until good people at xda find a way.
Also, flashing a rom twice will confirm the fact that the rom is on both the partitions since different part of the phone use different partitions.
Click to expand...
Click to collapse
But I did a "clean flash" over and over again and it never worked. The only reason I eventually flashed boot.img was because none of the traditional methods worked.
Nokoff said:
But I did a "clean flash" over and over again and it never worked. The only reason I eventually flashed boot.img was because none of the traditional methods worked.
Click to expand...
Click to collapse
I have no idea.
The transition from Color OS to Oxygen must be done through a rollback to a rollback firmware. From Android 12 Color OS to Android 12 Oxygen and only subsequently updated accordingly to Android 13 Oxygen.
You can downgrade the firmware through a local update, but the transition can only be done through Fastboot Enhancement.
I have had " the phone going to crash dump" before . What did to get out of that was get back to fastboot .
Use command ( fastboot getvar current-slot ) . If it was on A ... I used command ( fastboot set_active other ). Then I would reboot to other slot .. That worked for me
Canuck Knarf said:
I have had " the phone going to crash dump" before . What did to get out of that was get back to fastboot .
Use command ( fastboot getvar current-slot ) . If it was on A ... I used command ( fastboot set_active other ). Then I would reboot to other slot .. That worked for me
Click to expand...
Click to collapse
yes it does, often times. I'll remember this next time.