Database Develop

HTC Vivid Radio/Baseband issue

Hello,
I have searched multiple forums for hours today and have figured out what is going on with my HTC Vivid. (It has been upgraded to AT&T Official ICS.)
It was working fine up until yesterday where it was not receiving a signal from the mobile network and the signal icon has an X through it. The SIM card is properly inserted and another SIM card has been tried as well. Looking through other threads it seems like the Radio RIL files may be missing or corrupt. The IMEI number and *#06# code does not show an IMEI number either. The baseband version says unknown. I am not sure what happened as I have never loaded any other ROM on it.
I downloaded the Official RUU ICS upgrade ROM today and tried reflashing it, with no luck.
What is interesting (and the other person who had the radio problem) is that when I left the phone sit off overnight and then turned it on in the morning, the phone connected to the mobile network and I had a signal. When I restarted the phone, hours later, the phone lost connection to the mobile network and that is when I started digging and found the problem with the baseband version being unknown.
Is there anything anyone can suggest? Can I reflash the baseband files or copy them from someone somehow using ADB? It seems like there is where my problem lays. I've searched for ways on how to downgrade from ICS to the official GB stock rom, but it doesn't seem like it can be accomplished.
(I tried downloading the Holiday Cingular version of the GB stock rom but the update failed. I read about the ICS HBOOT version being different and not allowing it.)
Thank you in advance for helping and any suggestions.

Have you gotten a new sim card yet? That needs to be your first step. My captivate did the same thing and turned out the sim went bad
Sent from my HTC PH39100 using Tapatalk 2

Cor-master said:
Have you gotten a new sim card yet? That needs to be your first step. My captivate did the same thing and turned out the sim went bad
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Yes I have tried a different sim card. I don't believe thats the issue though being that it worked with the same sim after I let the phone sit overnight. From reading about others experience, it doesn't seem that the sim is the issue but more the baseband version and imei information missing.

centro7710 said:
Hello,
I have searched multiple forums for hours today and have figured out what is going on with my HTC Vivid. (It has been upgraded to AT&T Official ICS.)
It was working fine up until yesterday where it was not receiving a signal from the mobile network and the signal icon has an X through it. The SIM card is properly inserted and another SIM card has been tried as well. Looking through other threads it seems like the Radio RIL files may be missing or corrupt. The IMEI number and *#06# code does not show an IMEI number either. The baseband version says unknown. I am not sure what happened as I have never loaded any other ROM on it.
I downloaded the Official RUU ICS upgrade ROM today and tried reflashing it, with no luck.
What is interesting (and the other person who had the radio problem) is that when I left the phone sit off overnight and then turned it on in the morning, the phone connected to the mobile network and I had a signal. When I restarted the phone, hours later, the phone lost connection to the mobile network and that is when I started digging and found the problem with the baseband version being unknown.
Is there anything anyone can suggest? Can I reflash the baseband files or copy them from someone somehow using ADB? It seems like there is where my problem lays. I've searched for ways on how to downgrade from ICS to the official GB stock rom, but it doesn't seem like it can be accomplished.
(I tried downloading the Holiday Cingular version of the GB stock rom but the update failed. I read about the ICS HBOOT version being different and not allowing it.)
Thank you in advance for helping and any suggestions.
Click to expand...
Click to collapse
I had a similar problem and thought I solved it, but I later realised all my "solutions" didn't bring back the network but coincided with its reappearing cos no same "solution" worked more than once.
It's a very weird problem as the network shows up once in a while and when I'm using Mobile Network for Data, my phone hangs again and the IMEI, Network, baseband disappears on reboot...till further notice. I gave up trying and concluded it's either a bad modem (hardware) or something AT&T knows about!
You can get HBOOTS for both GB and ICS via Hasoons AIO kit
Flash the HBOOT, Flash the Image from Cingular GB RUU and I wish you luck!!!

ayulatins said:
I had a similar problem and thought I solved it, but I later realised all my "solutions" didn't bring back the network but coincided with its reappearing cos no same "solution" worked more than once.
It's a very weird problem as the network shows up once in a while and when I'm using Mobile Network for Data, my phone hangs again and the IMEI, Network, baseband disappears on reboot...till further notice. I gave up trying and concluded it's either a bad modem (hardware) or something AT&T knows about!
You can get HBOOTS for both GB and ICS via Hasoons AIO kit
Flash the HBOOT, Flash the Image from Cingular GB RUU and I wish you luck!!!
Click to expand...
Click to collapse
I found the download link, but the website says they're updating their drives, so who knows how much longer that will take.
Also, are you saying I should just use the tools within the kit to flash the HBOOT back to the previous version compatible with GB and then flash the RUU GB image after? Can I do that with the phone connected via USB or does it have to be flashed from the SD card? If it has to be flashed from the SD card, how do I go about doing that? If it can be done from the phone via USB, does the phone have to be in recovery mode?
I have tried reflashing the ICS RUU multiple times w/ version 3.26.502.52 and 3.26.502.56, both do not fix the issue. Do the baseband and or radio files NOT get flashed within these updates?
Thanks for the response!

centro7710 said:
I tried finding a download link for the AIO kit on the link provided, but I must be blind?
Also, are you saying I should just use the tools within the kit to flash the HBOOT back to the previous version compatible with GB and then flash the RUU GB image after? Can I do that with the phone connected via USB or does it have to be flashed from the SD card? If it has to be flashed from the SD card, how do I go about doing that? If it can be done from the phone via USB, does the phone have to be in recovery mode?
I have tried reflashing the ICS RUU multiple times w/ version 3.26.502.52 and 3.26.502.56, both do not fix the issue. Do the baseband and or radio files NOT get flashed within these updates?
Thanks for the response!
Click to expand...
Click to collapse
For any issues downloading Hasoon AIO tool, please use his thread (earlier provided).
Yes, use the AIO tool to flash GB HBOOT or read the SUPERGUIDE
and obtain rom.zip from the Cingular RUU
I don't know how to flash RUU via Recovery [email protected]@@!!!
I'd advice you follow my first solution here!!!

ayulatins said:
For any issues downloading Hasoon AIO tool, please use his thread (earlier provided).
Yes, use the AIO tool to flash GB HBOOT or read the SUPERGUIDE
and obtain rom.zip from the Cingular RUU
I don't know how to flash RUU via Recovery [email protected]@@!!!
I'd advice you follow my first solution here!!!
Click to expand...
Click to collapse
Thanks for the quick reply.
Your thread was the one I saw earlier with the simliar problem that I am having, only I have not loaded any custom ROMS. The phone just stopped receiving the signal the other day. I am still waiting for the download website to become available to use the tool to perform the flash of HBOOT, however, once I do that, will that erase the ICS rom from my phone? If so, what steps do I have to perform to get it in a "download mode" to accept the AT&T GB RUU? I'm a little confused on that part.
I read your first thread and I am a bit confused on exactly how you were able to correct the baseband/RIL issue (which I am assuming is the root of my issue). Do I have to extract some files from the RUU executable? Are the commands you provided to be used in ADB? I am confused as to what to do with [setprop ro.baseband 3.26.5XXX (<--- mainver: in android-info.txt in RUU.zip)] from your post. If that command is copying a file or just setting information (almost like as a registry setting within Windows) to point to the file or set a version number. Also if the XXX needs to have a certain number.
I thank you for your time and am trying my hardest to understand what to do to accomplish these steps.

centro7710 said:
Thanks for the quick reply.
Your thread was the one I saw earlier with the simliar problem that I am having, only I have not loaded any custom ROMS. The phone just stopped receiving the signal the other day. I am still waiting for the download website to become available to use the tool to perform the flash of HBOOT, however, once I do that, will that erase the ICS rom from my phone? If so, what steps do I have to perform to get it in a "download mode" to accept the AT&T GB RUU? I'm a little confused on that part.
I read your first thread and I am a bit confused on exactly how you were able to correct the baseband/RIL issue (which I am assuming is the root of my issue). Do I have to extract some files from the RUU executable? Are the commands you provided to be used in ADB? I am confused as to what to do with [setprop ro.baseband 3.26.5XXX (<--- mainver: in android-info.txt in RUU.zip)] from your post. If that command is copying a file or just setting information (almost like as a registry setting within Windows) to point to the file or set a version number. Also if the XXX needs to have a certain number.
I thank you for your time and am trying my hardest to understand what to do to accomplish these steps.
Click to expand...
Click to collapse
I did find the extracted files within the RUU executable and found the rom.zip which included the .img files among other files I assume needed as sources to flash the phone. I see a radio.img file would I be able to do anything with that?
Thank you.

centro7710 said:
I did find the extracted files within the RUU executable and found the rom.zip which included the .img files among other files I assume needed as sources to flash the phone. I see a radio.img file would I be able to do anything with that?
Thank you.
Click to expand...
Click to collapse
And I have a question, if the radio/baseband files are included in the RUU flash, what is happening as to why it is not being reflashed, or if it is being reflashed, why it is disabling the mobile network and providing an Unknown version to Baseband and clearing the IMEI number?

ayulatins said:
For any issues downloading Hasoon AIO tool, please use his thread (earlier provided).
Yes, use the AIO tool to flash GB HBOOT or read the SUPERGUIDE
and obtain rom.zip from the Cingular RUU
I don't know how to flash RUU via Recovery [email protected]@@!!!
I'd advice you follow my first solution here!!!
Click to expand...
Click to collapse
Here's where I am:
I successfully unlocked my bootloader, downgraded to GB, rooted. Tried to gain root access through adb terminal but it was not working properly.
I relocked my bootloader. Installed the ICS RUU AT&T ROM update. Unlocked my bootloader, rooted.
I see the commands you ran in your previous post. I am also receiving the same message of N/A when running the getprop ro.baseband
I tried the second command setprop ro.baseband 3.26.5XXX and then restarted the phone. I have tried it as posted, and also with swapping out the version that is located in my android-info.txt file: 3.26.502.56
Still no luck with setting the baseband version. IMEI still is cleared out.
Am I doing something wrong?

ayulatins said:
I had a similar problem and thought I solved it, but I later realised all my "solutions" didn't bring back the network but coincided with its reappearing cos no same "solution" worked more than once.
It's a very weird problem as the network shows up once in a while and when I'm using Mobile Network for Data, my phone hangs again and the IMEI, Network, baseband disappears on reboot...till further notice. I gave up trying and concluded it's either a bad modem (hardware) or something AT&T knows about!
Click to expand...
Click to collapse
Please see my initial quotes above...
All the previous steps I took were only a coincidence (not proven to work)!!!
We may need to contact AT&T to be sure its not a lock IMEI (and I'm wondering why it would be) or an experienced Dev

ayulatins said:
Please see my initial quotes above...
All the previous steps I took were only a coincidence (not proven to work)!!!
We may need to contact AT&T to be sure its not a lock IMEI (and I'm wondering why it would be) or an experienced Dev
Click to expand...
Click to collapse
Hey thanks for all of your suggestions. I contacted AT&T the day everything happened to see if it was on the block list. They said no. I tried multiple things including trying to re-flash the radio, but I was getting a signature failed error that I could not get around. I really think that's what the problem is. I gave up and ended up selling it.

centro7710 said:
Hey thanks for all of your suggestions. I contacted AT&T the day everything happened to see if it was on the block list. They said no. I tried multiple things including trying to re-flash the radio, but I was getting a signature failed error that I could not get around. I really think that's what the problem is. I gave up and ended up selling it, as is, on ebay instead to get a few bucks out of it and getting a new phone.
Click to expand...
Click to collapse
I really wouldn't mind selling mine too if I get a buyer. I'm just tired of all the troubles and no dev is willing to help.

ayulatins said:
I really wouldn't mind selling mine too if I get a buyer. I'm just tired of all the troubles and no dev is willing to help.
Click to expand...
Click to collapse
Exactly. It was my sister's phone. The sh*tty thing is we bought two off of ebay at the same time, 1 for me, 1 for her. Well, her phone was not in the box (either never shipped or stolen) so I had to file a claim through eBay which took 3 weeks to get the money back. Meanwhile, I gave her my phone (which is the phone in reference) to use instead. I bought her an iPhone instead now, along with purchasing one myself. I loved Android, but the bugs and fragmentation is getting too much for me to handle.

Dude, if you don't have an IMEI showing up, something is WAY wrong. That goes beyone the RIL not working... The RIL is probably fine. If your phone doesn't have an IMEI somehow, the cell towers are NOT, NO WAY, NEVER EVER going to register your phone on their network. You can put a billion SIM cards in there, or flash a billion stock ROMS, and if you don't have an IMEI, you will never be able to connect.
Something is probably corrupt or broken in your firmware or the hardware itself. I think your device is probably screwed.
My advice, is follow the steps to put your phone back to stock (including changing the bootloader message back to **LOCKED** and S-ON), and get it back to the phone company. They will be able to tell something is boned on the phone right away since it isn't displaying an IMEI.
Sorry to be the bearer of bad news and for your many wasted hours... But on the plus side, you now know a LOT about flashing and how your phone works now
Good luck with everything man! Hope they get you up and running soon!

I have the same problem as the OP but I have a IMEI showing up and a Basehand But won't connect to AT&T or anything they resent me a Signal & everything it shows a X with no bars it happened after I did a Factory Reset

anyone got the Radio.img?

inick73376 said:
I have the same problem as the OP but I have a IMEI showing up and a Basehand But won't connect to AT&T or anything they resent me a Signal & everything it shows a X with no bars it happened after I did a Factory Reset
Click to expand...
Click to collapse
That's weird..you try creating the apns again? I don't see how a factory reset would do that. Try toggling airplane mode too
Sent from my De-Sensed HTC Vivid using xda premium

I am currently having the same issues right now, it works if i leave the phone off for 1 hr it will work until i reboot then its down again, tried every thing possible, airplane mode will crash, reflashing the radios from gb and ics does nothing, setprop does nothing really. from this point it feels like a hardware issue.
sorry to revive an old thread, i just wanted to know if anyone came across this issue and had it fixed
i will get a log to see if there is errors showing up

Return it.
Sent from my HTC Holiday using Tapatalk 2

HELP: Upgraded from stock 4.2.2 to 4.4 and lost network connectivity

Hello All,
Tried searching for a case peculiar as mine, wasnt able to find one so here is the lowdown.
1. Xperia C6603 , originally had 4.2.2 stock ROM which was working fine with my local network. Dont remember the baseband version.
2. Used XperiFirm to download the latest firmware as reported in the list. Dont know what does the suffix RxD (R1D--R8D) means. Anyone please explain. As per the below screenshot downloaded version "C6603_Customized HK_1270-5695_10.5.1.A.0.292_R1D" .
3. Before flashing the downloaded firmware I flashed the dualrecovery from XZDualRecovery. I made a TWRP backup of the 4.2.2 stock ROM on an external SD card, for all partitions including TA,system,boot etc.
4. Used Flashtool to convert the downloaded (step 2) firmware "FILES" format to a flashable FTF file. Flashed the firmware , which went on smoothly.
5. At the first startup I got the following screen , telling me that it is a prototype device/firmware . I went on to see that the network which was working fine with stock ROM 4.2.2 was no longer available.
I tried to go to settings to check and search for networks, which shows available networks, but unable to get itself registered to the SIM providers network. Tried all the settings combinations in menu "*#*#4636*#*#" , nothing makes it work to get the GSM network connectivity back. It is supposedly on the correct setting of LTE/WCDMA/GSM which my current operator supports. Following is the "About" screen for current baseband version.
Tried going in the "Service" menu via "*#*#7378423#*#*" , with the following info, having an unknown modem configuration.
6. Tried reverting back to the old TWRP backup, for which I needed the TWRP recovery loaded on the phone. So ran the XZDualRecovery script again (with the new 4.4 ROM on the phone), however the script hangs around in the end and never reboots the phone with the TWRP recovery. So i am unable to revert and use the stock ROM backups .
7. I dont want to root/unlock the bootloader, however I tried installing TWRP via its "XZrecovery.apk", but it requires busybox (which requires a rooted phone). So i tried the rooting script from [GUIDE] How to root 10.5.1.A.0.283 / 10.5.1.A.0.292 [Locked Bootloader], but it also hangs around in the end and never delivers a rooted phone.
8. Tried looking around for assortment of xperia Z baseband files to check and see if flashing it separately can make it work, however to no avail the the condition persists.
Either ways having a prototype version on the phone which transmits all data back to sony is not desirable at all. So need to replace it for sure. Currently I am stuck in the middle without a clue of how to go back and restore the 4.2.2 TWRP backup, or to actually flash a "non-prototype" or retail version of 4.4.x .
Any help/guidance/suggestions to remedy would be appreciated.
Thanks.
=====================UPDATE
Ok followed the instructions at [GUIDE] How to root 10.5.1.A.0.283 / 10.5.1.A.0.292 [Locked Bootloader] , read carefully again to flash the .230 kernel. Flashed the XZDualRecovery and got the TWRP recovery back.
Restored the old 4.2.2 TWRP backup , hoping that everything would go back to normal. However with a successul restore and a reboot, I was amazed to see I still have no network connectivity. The baseband version is "9x15A-ACEFWMAZQ-30110068-44" . Another noticeable thing was that after the restore and first boot, I still got the "prototype device" message again, which was not there when I first booted the device with original stock 4.2.2 ROM before this flashing adventure began.
Any ideas what may have gone bad.
Thanks.
=======================================
Just got to know that my device is a BROWN device, its IMEI number starts from 0044 so it is a prototype. Any ideas is it really good or bad to have one. Also I see that after another restore of the original stock 4.2.2 ROM it is barely getting the signals indoor (1 bar only). The signal reception is very weak and sporadic . Should i keep the device or not and is there any remedy or network signal strength.
Thanks.

HyperEscape said:
Hello All,
Tried searching for a case peculiar as mine, wasnt able to find one so here is the lowdown.
1. Xperia C6603 , originally had 4.2.2 stock ROM which was working fine with my local network. Dont remember the baseband version.
2. Used XperiFirm to download the latest firmware as reported in the list. Dont know what does the suffix RxD (R1D--R8D) means. Anyone please explain. As per the below screenshot downloaded version "C6603_Customized HK_1270-5695_10.5.1.A.0.292_R1D" .
3. Before flashing the downloaded firmware I flashed the dualrecovery from XZDualRecovery. I made a TWRP backup of the 4.2.2 stock ROM on an external SD card, for all partitions including TA,system,boot etc.
4. Used Flashtool to convert the downloaded (step 2) firmware "FILES" format to a flashable FTF file. Flashed the firmware , which went on smoothly.
5. At the first startup I got the following screen , telling me that it is a prototype device/firmware . I went on to see that the network which was working fine with stock ROM 4.2.2 was no longer available.
I tried to go to settings to check and search for networks, which shows available networks, but unable to get itself registered to the SIM providers network. Tried all the settings combinations in menu "*#*#4636*#*#" , nothing makes it work to get the GSM network connectivity back. It is supposedly on the correct setting of LTE/WCDMA/GSM which my current operator supports. Following is the "About" screen for current baseband version.
Tried going in the "Service" menu via "*#*#7378423#*#*" , with the following info, having an unknown modem configuration.
6. Tried reverting back to the old TWRP backup, for which I needed the TWRP recovery loaded on the phone. So ran the XZDualRecovery script again (with the new 4.4 ROM on the phone), however the script hangs around in the end and never reboots the phone with the TWRP recovery. So i am unable to revert and use the stock ROM backups .
7. I dont want to root/unlock the bootloader, however I tried installing TWRP via its "XZrecovery.apk", but it requires busybox (which requires a rooted phone). So i tried the rooting script from [GUIDE] How to root 10.5.1.A.0.283 / 10.5.1.A.0.292 [Locked Bootloader], but it also hangs around in the end and never delivers a rooted phone.
8. Tried looking around for assortment of xperia Z baseband files to check and see if flashing it separately can make it work, however to no avail the the condition persists.
Either ways having a prototype version on the phone which transmits all data back to sony is not desirable at all. So need to replace it for sure. Currently I am stuck in the middle without a clue of how to go back and restore the 4.2.2 TWRP backup, or to actually flash a "non-prototype" or retail version of 4.4.x .
Any help/guidance/suggestions to remedy would be appreciated.
Thanks.
=====================UPDATE
Ok followed the instructions at [GUIDE] How to root 10.5.1.A.0.283 / 10.5.1.A.0.292 [Locked Bootloader] , read carefully again to flash the .230 kernel. Flashed the XZDualRecovery and got the TWRP recovery back.
Restored the old 4.2.2 TWRP backup , hoping that everything would go back to normal. However with a successul restore and a reboot, I was amazed to see I still have no network connectivity. The baseband version is "9x15A-ACEFWMAZQ-30110068-44" . Another noticeable thing was that after the restore and first boot, I still got the "prototype device" message again, which was not there when I first booted the device with original stock 4.2.2 ROM before this flashing adventure began.
Any ideas what may have gone bad.
Thanks.
=======================================
Just got to know that my device is a BROWN device, its IMEI number starts from 0044 so it is a prototype. Any ideas is it really good or bad to have one. Also I see that after another restore of the original stock 4.2.2 ROM it is barely getting the signals indoor (1 bar only). The signal reception is very weak and sporadic . Should i keep the device or not and is there any remedy or network signal strength.
Thanks.
Click to expand...
Click to collapse
Firstly I love the detail you have provided which would save you and me a lot of time to pinpoint the exact problem and work it accordingly.
Firstly, I would suggest that if you have a box or any other receipt that shows your exact device name with its basebands. Where did you buy it from and what is your exact location so we can guess your region. This is the time to show it now. Also which basebands work in your location can also help us out.
The problem you have made it flashed basebands of a different variant which has resulted in loss of network. So to fix it we need, and there are three ways about it.
First, download Sony PC companion and try to repair your phone and see if that helps.
Secondly, download flashtool and ftf for your device (make sure you select the right variant this time. Choosing for wrong device can hard brick your phone. so beware) and flash your phone with it.
If all this fails, you go to Sony flashtool called Emma. Download it and try to flash it with that.
You can google how to use every tool on xda and I am sure you would find a lot of guides for that.
Quote me back in case you expect an answer

Optimus L90 Unable to Root, Unable to boot into recovery mode

Hi
I have gone through the forums and can't seem to find solution for my problem with my Optimus L90 phone.
I have recently flashed the CM13 on my phone without any errors but below are the issues that I am facing
1. No cellular network signal after inserting SIM card.
2. I read in a different forum that this could happen due to using a wrong version of TWRP, so installed a newer version 2.8.7.0 but things worse.
3. Now I am not able to boot into recovery mode and phone just stays idle with the LG logo screen and few commands appearing like fastboot_iniy() and udc_start().
4. I have tried hard reset and soft reset and both are not successful.
5. I cannot root my phone either. Tried all ways like towelroot, purpledrake, lg root by avicoh etc but in vain
Now my phone, even though has a latest CM version I cannot use it for anything else.
Any help is greatly appreciated.

No SIM is hardly related to TWRP, probably you needed a different bootstack (there is a thread about it).
On CM you don't need anything to root, it's already rooted just not visible to common users, you need to activate Developer Options (it's also explained elsewhere)
Finally, if you cannot reach recovery but still can boot CM13 simply use adb, Flashfy or Hashr to flash another version or TWRP. 2.8.7 is kinda old and not recommended for Marshmallow, you can try 3.0.2 by SlimShady or DarkBlue version from shoxxy's thread.

Thanks for the reply, let me try options you have specified and get back if I am still facing issues

hvramanan said:
Thanks for the reply, let me try options you have specified and get back if I am still facing issues
Click to expand...
Click to collapse
I was able to unblock my phone finally and loaded the stock ROM but the phone is still isn't recognizing cellular network . I am on T-MOBILE. I have tried to insert different SIM, turned off wifi calling but still the phone is not catching any cellular network.
[lfom]: you indicated earlier that a different bootstack might be needed. I am not that knowledgeable about bootstack so can you help me through this or point me to different thread where users might have a similar issue.

Sorry, I meant to say unbrick above

Everything one needs or wants to know about bootstack is here:
http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632

lfom said:
Everything one needs or wants to know about bootstack is here:
http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632
Click to expand...
Click to collapse
Hi,
I followed the steps mention in the above thread to change the bootstack and was able to complete it without any issues, however the problem still persists and my phone is not recognizing the SIM and does not catch the cellular network.
Previously I used to use this phone with my t-mobile number and after I took a new phone haven't been using it for sometime. I want to sell this phone and was trying to ensure that it works fine and thats when I saw that the phone is not catching any cellular networks.
Please help. Let me know if you need any other details to better diagonize the problem.

hvramanan said:
Hi,
I followed the steps mention in the above thread to change the bootstack and was able to complete it without any issues, however the problem still persists and my phone is not recognizing the SIM and does not catch the cellular network.
Previously I used to use this phone with my t-mobile number and after I took a new phone haven't been using it for sometime. I want to sell this phone and was trying to ensure that it works fine and thats when I saw that the phone is not catching any cellular networks.
Please help. Let me know if you need any other details to better diagonize the problem.
Click to expand...
Click to collapse
You didn't say what model you have, maybe you flashed the wrong bootstack for your model (hardware version)? Be very careful, you can hart brick your device, and if it's a D415 it's very hard to unbrick. I'd suggest that first you make sure what model you have by removing the battery and looking in the label below, it says what model you have. Then, use LG Flash Tool to flash stock ROM (KDZ) to latest KitKat, then flash Lollipop or use OTA to update to latest version. The only requirements are that you make sure what model you have and flash the corresponding version, and the phone is still able to enter download mode.

lfom said:
You didn't say what model you have, maybe you flashed the wrong bootstack for your model (hardware version)? Be very careful, you can hart brick your device, and if it's a D415 it's very hard to unbrick. I'd suggest that first you make sure what model you have by removing the battery and looking in the label below, it says what model you have. Then, use LG Flash Tool to flash stock ROM (KDZ) to latest KitKat, then flash Lollipop or use OTA to update to latest version. The only requirements are that you make sure what model you have and flash the corresponding version, and the phone is still able to enter download mode.
Click to expand...
Click to collapse
[lfom]: thank you for responding. My phone model is LG-D415 . Actually my phone was bricked but I was able to get into download mode and then I used the L90 Hardbrick tool to flash stock ROM (KDZ) to latest kitkat like you have specified above. Then with the OTA update I was able update it to latest lollipop. Then I followed this forum below to to change the bootstack to KK 10C version as the issue specified in the below thread was similar to mine.
http://forum.xda-developers.com/lg-l90/development/rom-cyanogenmod-12-lg-l90-t3049512/page235
Image of the label inside my phone attached.
Do you think I should have used the LG flash tool to flash stock ROM. Should I repeat the steps with the LG flash tool ?
Thank you again for helping me on this.

Do you see your IMEI in the about phone page? Does it match the one in the label? Maybe when you bricked you've lost the phone's IMEI, and you can't get it back just flashing ROM...

lfom said:
Do you see your IMEI in the about phone page? Does it match the one in the label? Maybe when you bricked you've lost the phone's IMEI, and you can't get it back just flashing ROM...
Click to expand...
Click to collapse
Yes I checked and it matches. There two fields IMEI which has the number and then there is another field which says IMEI SV and it has a value of 02 in it.

MOTO G6 - IMEI 'Unknown', Baseband 'Unknown' - NEED HELP PLEASE!

Hello everyone, I am new to all of this development stuff for Android devices and I know I screwed something up big time.
I had an update recently on my Moto G6 XT1925-6 phone to Pie and there were several bugs happening from calls dropping, data and service dropping erratically, youtube videos would skip forward several times or not download at all. I found the post on here to downgrade from Pie to Oreo Stock ROM and followed it exactly as I could. Everything went according to the guide, but now after rebooting the phone and going through the setup, the phone wont detect my SIM, and there is no service. Under the IMEI Information, everything is 'Unknown' and under SIM status everything says 'Not Available'. Also, under Mobile Network, Data Roaming, Preferred network type, and System select is greyed out. CDMA subscription is the only thing available to tap. The issue with that is, this phone is originally GSM.
Please, I am not knowledgeable in messing with Android systems and I know I shouldn't be messing with something I know nothing about. I do have ADB Minimum installed on my PC, the phone is unlocked bootloader but is currently not rooted after the stock ROM was flashed.
Stock ROM: ALI_RETAIL_8.0.0_OPSS27.104-92-4-5-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
One more thing to add, I did the fastboot IMEI check command and it came back with one IMEI so it is still present in the phone somewhere.
Any help would be greatly appreciated! Thanks in advance!

Angelo Della Morte said:
Hello everyone, I am new to all of this development stuff for Android devices and I know I screwed something up big time.
I had an update recently on my Moto G6 XT1925-6 phone to Pie and there were several bugs happening from calls dropping, data and service dropping erratically, youtube videos would skip forward several times or not download at all. I found the post on here to downgrade from Pie to Oreo Stock ROM and followed it exactly as I could. Everything went according to the guide, but now after rebooting the phone and going through the setup, the phone wont detect my SIM, and there is no service. Under the IMEI Information, everything is 'Unknown' and under SIM status everything says 'Not Available'. Also, under Mobile Network, Data Roaming, Preferred network type, and System select is greyed out. CDMA subscription is the only thing available to tap. The issue with that is, this phone is originally GSM.
Please, I am not knowledgeable in messing with Android systems and I know I shouldn't be messing with something I know nothing about. I do have ADB Minimum installed on my PC, the phone is unlocked bootloader but is currently not rooted after the stock ROM was flashed.
Stock ROM: ALI_RETAIL_8.0.0_OPSS27.104-92-4-5-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
One more thing to add, I did the fastboot IMEI check command and it came back with one IMEI so it is still present in the phone somewhere.
Any help would be greatly appreciated! Thanks in advance!
Click to expand...
Click to collapse
What version of Pie did you upgrade to and when you downgraded did you flash the bootloader and gpt.bin files? Can you link the post that you followed?

kc6wke said:
What version of Pie did you upgrade to and when you downgraded did you flash the bootloader and gpt.bin files? Can you link the post that you followed?
Click to expand...
Click to collapse
First, thank you for your reply and help in this matter!
After the update from the phone itself, it said it was Android Pie v9.0.0. I don't know anything further than that on which version of Pie if there are several.
When I attempted to flash the bootloader and the gpt.bin during the steps on the forum guide, adb gave me the 'couldn't open' and the 'Failed' result for those two things. Reading one of the replies to this guide, someone stated that they didn't flash either of those and it worked perfectly.
Here is the guide: https://forum.xda-developers.com/moto-g6/how-to/guide-faster-updated-guide-to-root-t3914228

Angelo Della Morte said:
First, thank you for your reply and help in this matter!
After the update from the phone itself, it said it was Android Pie v9.0.0. I don't know anything further than that on which version of Pie if there are several.
When I attempted to flash the bootloader and the gpt.bin during the steps on the forum guide, adb gave me the 'couldn't open' and the 'Failed' result for those two things. Reading one of the replies to this guide, someone stated that they didn't flash either of those and it worked perfectly.
Here is the guide: https://forum.xda-developers.com/moto-g6/how-to/guide-faster-updated-guide-to-root-t3914228
Click to expand...
Click to collapse
I have successfully downgraded from Pie PPSS29.55-24-2 to Oreo without flashing those files but today when I flashed the newest Pie PPS29.118-11-1, I got these results.
Only solution was to reflash the latest Pie. If you took the OTA update as it appears you did you are most likely in the same boat I'm in stuck on the latest Pie.

kc6wke said:
I have successfully downgraded from Pie PPSS29.55-24-2 to Oreo without flashing those files but today when I flashed the newest Pie PPS29.118-11-1, I got these results.
Only solution was to reflash the latest Pie. If you took the OTA update as it appears you did you are most likely in the same boat I'm in stuck on the latest Pie.
Click to expand...
Click to collapse
Okay, thank you for the information. Unfortunately I will have to reupdate to P.O.S. Pie. Could you point me to the correct version of Pie that will work? It was the OTA update to PIE that I did so if you could let me know which one you labeled would work, then I can get started. Maybe point me to a guide if you know of one to do it properly.
Thanks a million!

Angelo Della Morte said:
Okay, thank you for the information. Unfortunately I will have to reupdate to P.O.S. Pie. Could you point me to the correct version of Pie that will work? It was the OTA update to PIE that I did so if you could let me know which one you labeled would work, then I can get started. Maybe point me to a guide if you know of one to do it properly.
Thanks a million!
Click to expand...
Click to collapse
I can't tell you exactly which firmware to download, but It looks like you are using the Retail version by your post mentioning "Stock ROM: ALI_RETAIL_8.0.0_OPSS27.104-92-4-5-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml". If so I would flash this one.
As for a guide some people use RSD lite but I prefer this method.
download the attachment and extract it
extract the firmware to the folder Place_Extracted_Firmware_Here.
double click 2-rsd-flash-flashfile-windows.bat, this will create a file called flashfile.bat (It will Wipe your data).
boot your phone to bootloader, connect it to pc.
double click the flashfile.bat and let it run
reboot
hope this helps
View attachment RSD_Lite_Motorola_XML_To_Batch_Script.zip

351849091444336

Please help! Flashing AT&T N960U firmware on N960U1 device with Android 10

Hi guys,
I have a question about obtaining Android 10 AT&T firmware for the SM-960U. I'm currently having an issue where I bought the Samsung Galaxy Note 9 N960U1 factory unlocked from Samsung themselves. My current carrier is AT&T. However, I've realized for a while that my area doesn't have a good signal (1 bar to no service) due to the location where I am. I am trying to install AT&T's firmware with the boot logo and its software's bloatware to obtain Wi-Fi calling. However, I am having trouble. Currently, I've flashed my N960U1 with AT&T's U1 Android 10 firmware from the site using Odin. I see that it's been flashed successfully after doing a clean install and see AT&T firmware in the phone. However, it did not give me an AT&T boot logo screen or give me the Wi-Fi calling option. This is carrier unbranded. It's still the same like it's from the factory unlock no carrier firmware. So, after doing some research, I see that what I have to do is: clean flash AT&T's U1 firmware on the device (which I did), then, finally, install the U firmware to bring on the AT&T boot logo screen and WiFi calling. However, I am unable to do the 2nd part, because the only available firmware for U firmware (AT&T's bloatware) is Android 8. Due to the bootloader being version 4 in Android 10 and version 2 in android 8, I cannot downgrade even on a cracked Odin version. The phone gives me a SW REV error and odin gives me a write error. I worked on this for 8 hours, don't try to fight me on this lol. This is because Odin understands that the phone can't be downgraded due to the bootloader version being higher. This can be seen in the firmware names when comparing (Android 8: N960USQU1ARG6. Android 10: N960U1UES4DTD1).
In summary, I need to find the SM-960U AT&T carrier-branded Android 10 firmware. Right now, on Sam Mobile for N960U, the only firmware that comes up is Android 8. Downloading the latest firmware for the SM-N960U1 on Sam Mobile doesn't help me obtain wifi calling and the AT&T boot logo. Any suggestions? I really need help and appreciate it if you guys could help me. I can't find AT&T's U anywhere. Thanks!

You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk

butchieboy said:
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Awesome. I’m going to try this tomorrow. I’ll update this post with the results! Thanks for the help.

butchieboy said:
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!

robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader:
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer port also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just updated.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
I am really glad I found your post and I'm going to attempt this same procedure today. Quick question, does it matter if / when your SIM is inserted into the phone? Just wondering if I need to leave it in or out during this process or whether that will even have an affect? Is your Wi-Fi calling still working currently, btw?

Carl_Sagan_Cosmos said:
I am really glad I found your post and I'm going to attempt this same procedure today. Quick question, does it matter if / when your SIM is inserted into the phone? Just wondering if I need to leave it in or out during this process or whether that will even have an affect? Is your Wi-Fi calling still working currently, btw?
Click to expand...
Click to collapse
Hey Carl! Sorry for the late response. I'm glad you found my post as well!
I apologize for this, I should've mentioned this in my original post: please leave the AT&T SIM card inserted in the device the entire time during this process! When the phone reboots after Odin flashes, the first thing it searches for is what SIM is inserted so it can flash the appropriate carrier setting. Do not remove the SIM during any part of the process from start to finish.
Secondly, yes! The WiFi calling feature is working great on the phone. I'm glad after two years of having the phone I was able to get the feature this month. Good luck. Please let me know if you were successful in flashing the firmware, I'd really like to hear your results! My notifications are turned back on for this thread.

robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
What to do if i don't have at&t sim card, not even usa sim card, i'm in egypt and brought my n960u from usa, i installed u1 firm but realized that no wifi calling or volte so tried to install tmobile carrier firm and nothing appeared then tried at&t and also nothing appeared, neither the options nor the boot logo for tmobile or at&t.
what to do please help!
Thanks in advance

abulnass said:
What to do if i don't have at&t sim card, not even usa sim card, i'm in egypt and brought my n960u from usa, i installed u1 firm but realized that no wifi calling or volte so tried to install tmobile carrier firm and nothing appeared then tried at&t and also nothing appeared, neither the options nor the boot logo for tmobile or at&t.
what to do please help!
Thanks in advance
Click to expand...
Click to collapse
If you are trying to flash T-Mobile or AT&T bloat ware without a carrier SIM card, it will not work.

Hi. What if I have an AT&T sim card, but I'm also outside US. Not sure if the sim card is active or not.
My biggest worry was, I just had my phone factory unlocked so I can use a local sim card here in the country.
Will this work? And if it will, will my phone go back to being locked by AT&T?

Hi, I tried this process the way you have it listed and it is not working. I keep getting a device info error in Odin. Tried the newest firmware and an older version

robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
right at the beginning using odin it threw me an error, but it's probably because I used CSC home ...? How can I verify on Samsung Note 9 if I have an unlocked bootloader ..?
Edit: He used CSC not CSC home and an older version of odin. And I have a sim from Europe and it works great.

I need help, i have a sm n960u factory unlocked at&t branded using straight talk at&t sim. I have no volte or wifi calling settings. With special code they are greyed out and provisioned. Is there any way i can fix this issue?