MOTO G6 - IMEI 'Unknown', Baseband 'Unknown' - NEED HELP PLEASE! - Moto G6 Questions & Answers

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

Related

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

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.

Help with IMEI Unknown

Good morning,
This cellphone is from a cousin which already sent this phone twice to techservice and it came back this way. Everything seems to be working except that it has no IMEI and no baseband.
What I know is it was never flashed with custom images, just official ones and it is currently with Android 4.4.2.
Any ideas?
Thank you in advance!
fggs said:
Good morning,
This cellphone is from a cousin which already sent this phone twice to techservice and it came back this way. Everything seems to be working except that it has no IMEI and no baseband.
What I know is it was never flashed with custom images, just official ones and it is currently with Android 4.4.2.
Any ideas?
Thank you in advance!
Click to expand...
Click to collapse
Hi, easy way, go to play store and download this apk Network Mode, and change the frecuency of the radio, press the tree pionts ,select Automatic, let he apk works; when finished check your baseand and imei back again, cheers.
Hi! Thanks for your answer! I did exactly what you said, but when I try to select Automatic it just says it failed. Any ideas?!
Hummmm, if you try whit Euro or Usa banda?
Tried every single option, same result
The rom , is an update from a recovery or you douwnload the update fron the ROM?
As far as I know, the update was downloaded from within JellyBean.
One time have the same isue like you, I solved this way, ...............................................

Used P9 - Missing Stock Apps

Hello everyone!
I just bought an used P9 (EVA-L19) in pristine condition. It arrived with the nougat update but it is missing all Huawei apps. I don't think I really mind not having those (less bloat, hurray!), but I really want at least the camera app! What should I try? This thing is full stock (unrooted), and I'd rather keep it that way... Should I just flash the full stock firmware? HiSuite claims my phone is up to date, but I've got no idea how to check what build my current firmware is.
Thanks!
Oooh... the build seems to be NRD90M "test-keys", which appears to be an old beta build from my googling. Do I have to go back to MM and then upgrade to Nougat? Hopefully I can do all that without a custom recovery...
You have an intermediate firmware.
Search here the B378 for C432 if you want the european version (wich is working fine; some other last updates may have some problems - for example, with B383 me and others have problems with the battery).
Where are you from ??
Shymmy said:
You have an intermediate firmware.
Search here the B378 for C432 if you want the european version (wich is working fine; some other last updates may have some problems - for example, with B383 me and others have problems with the battery).
Where are you from ??
Click to expand...
Click to collapse
I'm from Brazil, but I know for a fact this phone isn't brazilian. It comes with a bunch of stuff written in spanish rather than portuguese, and a warranty certificate citing a bunch of spanish-spekaing latin american countries. I'm browsing through the forums and trying to find out what is my Cust yet. But thanks for the response.
Also, if I have to flash something, is it better to stick with Nougat or is Marshmallow more hassle-free?
(I've attached a screenshot of the status screen from Huawei P9 Tool, this is all the data I could gather so far)
I can't read the screenshot ...
On the "About the phone - Version number" what do you have ??
For example, mine has EVA-L19C432B378, where:
-EVA-L19 is the phone model (P9 dual sim);
-C432 is the european version;
-B378 is the firmware version.
Also, you can read that thread too ... https://forum.xda-developers.com/p9/how-to/how-to-downgrade-nrd90m-to-marshmallow-t3541400
Shymmy said:
I can't read the screenshot ...
On the "About the phone - Version number" what do you have ??
For example, mine has EVA-L19C432B378, where:
-EVA-L19 is the phone model (P9 dual sim);
-C432 is the european version;
-B378 is the firmware version.
Also, you can read that thread too ... https://forum.xda-developers.com/p9/how-to/how-to-downgrade-nrd90m-to-marshmallow-t3541400
Click to expand...
Click to collapse
All it says on "Version number" is "NRD90M test-keys". I've read that thread, but to downgrade you need a ROM, and without knowing my Cust ID I'm not sure which ROM I should get.
The screenshot shows my serial number (XVV7N16425001010), the model (EVA-L19 - Dual Sim 32GB Rom 3GB RAM) and a weird build string (eng.jenkin.20161230.130431)
absynte said:
Hello,
do you have dual sim , or single sim and NFC ?
Dual sim: EVA-L19 ou L29
Single sim and NFC EVA-L09 (Européan version)
Click to expand...
Click to collapse
Dual SIM EVA-L19 - No idea if I've got NFC or not. Can't find anything NFC-related on the menus, but it might be that I do not know where to look. Long time Windows Phone user here, just migrated back to Android :laugh:
absynte said:
NFC is an connectivity option.
If you don't have, you have dual sim
Click to expand...
Click to collapse
It does have dual SIM, and is the EVA-L19. So no NFC then. Does it help? I'm currently looking for debranding guides because I can't find what branding this phone originally had.
Oooh well... so far:
1- *#*#2846579#*#* doesn't work (nothing happens), can't enable Manufacturer mode for DC Unlocker
2- The HUAWEI EMUI site doesn't give me a bootloader unlock code, so can't unlock the bootloader with the official method
So, so far, I can't install TWRP, so I can't flash a C432 oeminfo.bin
Also, the Rollback instructions at https://forum.xda-developers.com/p9/how-to/rollback-eva-l19-android-7-0-emui-5-0-t3496091 fail, as the rollback intermediate firmware just fails at 5% claiming to be incompatible with my device.
Aside from blindly trying to flash random firmwares with the three button method, do you guys have ANY ideas at all? I need a rest, just wasted the whole day trying to get this damned thing fixed
Sad thing: even with a borked firmware install this is still orders of magnitude better than my old Lumia 930.
EDIT: GODDAMMIT, BLUETOOTH ALSO DOESN'T WORK!
absynte said:
Ok so you've got to google this or to find on xda some answers.
https://forum.xda-developers.com/p9/how-to/how-to-downgrade-nrd90m-to-marshmallow-t3541400
For exemple....2 or 3 clicks....
bye
Click to expand...
Click to collapse
I'll give the instructions of the first post a try, though they did not work for the OP.
EDIT: AAAAAND the 800mb file is downloading at 28kbps... this won't be fun
I'm not sure if it would've been better to edit the last post or add a new one, so if this is agains the rules (I've read them and couldn't find it), please inform me and I'll change things accordingly... buuuut.... IT WORKED.
The OP on the topic absynte pointed out never really posted the outcome of his issue and it looked like he never got it to work, so here is what I did:
Flashed the zip file
I flashed the zip file linked in this post through starting up with vol up + vol down + power. Exactly like the guy over there it did not solve my issue, but did uncover I had exactly the same build as him (EVA-L19C185B361 - Middle East / Asia)
Flashed the intermediate firmware
I download the correct intermediate firmware (C185B300) from here and flashed the same way. The *#*#... menu did not work (as in the menu itself didn't show up)
Flashed a MM build
I downloaded and flashed C185B180 for whatever reason (could've gone with tha latest MM build right away AFAIK). Worked great, all stock apps were there and so was bluetooth
Let the phone update itself through OTA
It updated itself to B210 (or B220, don't remember well) and then B385. Seems to be working fine, but I haven't given the battery a fair chance (constantly flashing and updating stuff) to judge its performance.
Thanks everyone for the help!
alexanrsousa said:
I'm not sure if it would've been better to edit the last post or add a new one, so if this is agains the rules (I've read them and couldn't find it), please inform me and I'll change things accordingly... buuuut.... IT WORKED.
The OP on the topic absynte pointed out never really posted the outcome of his issue and it looked like he never got it to work, so here is what I did:
Flashed the zip file
I flashed the zip file linked in this post through starting up with vol up + vol down + power. Exactly like the guy over there it did not solve my issue, but did uncover I had exactly the same build as him (EVA-L19C185B361 - Middle East / Asia)
Flashed the intermediate firmware
I download the correct intermediate firmware (C185B300) from here and flashed the same way. The *#*#... menu did not work (as in the menu itself didn't show up)
Flashed a MM build
I downloaded and flashed C185B180 for whatever reason (could've gone with tha latest MM build right away AFAIK). Worked great, all stock apps were there and so was bluetooth
Let the phone update itself through OTA
It updated itself to B210 (or B220, don't remember well) and then B385. Seems to be working fine, but I haven't given the battery a fair chance (constantly flashing and updating stuff) to judge its performance.
Thanks everyone for the help!
Click to expand...
Click to collapse
how u downgrade to MM?
spring80 said:
how u downgrade to MM?
Click to expand...
Click to collapse
I did exactly what I said in the last post: flashed C185B300 (from http://www.carbontesla.com/2016/11/downgrade-huawei-p9-nougat-marshmallow-os-middle-east-russia/), then flashed C185B180 (from http://www.carbontesla.com/2016/11/download-huawei-p9-b180-marshmallow-update-l09l19-middle-east/)
alexanrsousa said:
I did exactly what I said in the last post: flashed C185B300 (from http://www.carbontesla.com/2016/11/downgrade-huawei-p9-nougat-marshmallow-os-middle-east-russia/), then flashed C185B180 (from http://www.carbontesla.com/2016/11/download-huawei-p9-b180-marshmallow-update-l09l19-middle-east/)
Click to expand...
Click to collapse
thanks for your answer my friend , i will try and update u
---------- Post added at 01:56 PM ---------- Previous post was at 01:25 PM ----------
working my friend , but be sure to backup first because u will lost everything

SM-G900F - Need original firmware

Hi guys,
My S5 was on 6.0 and have upgraded to 9 Pie but something went wrong (or I screwed up something) and I need to re-upload the original firmware, unless you have better suggestion.
Currently, I have TWRP installed as well as Android 9, however, when I turn my S5 on, I get: Set Warranty Bit:Kernel
It stays there for 30 secs then the phone boots up and everything looks fine, it connects to wi-fi etc.
One other strange thing is that I get a message on the home screen saying: unsupported SanDisk SD Card
I tried a new one, same message.
Before I started this process, I connected the phone to my PC and copied both the Phone and the Card folders, so I am good, data wise.
Basically I was thinking to go back to the very first OS, I think 4.4.2 and then re-load Lineage 16 using TWRP.
If I read the baseband version # is: G900FXXU1ANCE
If the procedure above is correct, would you be able to provide me a link to download the firmware?
I tried all the known sites, but their speed sucks, so I thought to ask here as somebody may have a link.
I will use Odin latest version to install it.
Thank you!
Alex
Access to the original/official firmware for SM-G900F would be extremely helpful for me as well.
I'm running LOS 16 with pico GApps very happily on my S5, however I have mobile data connectivity issues. Data connects and disconnects at random; this is device-dependent (swapping the SIM into other devices gives fully functional data connectivity).
My baseband is G900FXXU1BOA3; I believe updating the modem might fix this?
kwajongen said:
Hi guys,
My S5 was on 6.0 and have upgraded to 9 Pie but something went wrong (or I screwed up something) and I need to re-upload the original firmware, unless you have better suggestion.
Currently, I have TWRP installed as well as Android 9, however, when I turn my S5 on, I get: Set Warranty Bit:Kernel
It stays there for 30 secs then the phone boots up and everything looks fine, it connects to wi-fi etc.
One other strange thing is that I get a message on the home screen saying: unsupported SanDisk SD Card
I tried a new one, same message.
Before I started this process, I connected the phone to my PC and copied both the Phone and the Card folders, so I am good, data wise.
Basically I was thinking to go back to the very first OS, I think 4.4.2 and then re-load Lineage 16 using TWRP.
If I read the baseband version # is: G900FXXU1ANCE
If the procedure above is correct, would you be able to provide me a link to download the firmware?
I tried all the known sites, but their speed sucks, so I thought to ask here as somebody may have a link.
I will use Odin latest version to install it.
Thank you!
Alex
Click to expand...
Click to collapse
Fox, you may download the official firmware at https://samsung-firmware.org/model/SM-G900F/
Select your region to get the right ***.md5.tar file to flah via Odin latest.
This will reset your handheld to out of box - original recovery reinstalled - you must reflash it also via Odin if you want to go back to custom Rom..
Good luck
.
Thank you.
What would be my region?
I purchased it in the US unlocked, but US is not a choice when it comes to region.
Would I be able to see the region the phone is from from the baseband #?
Alex
kwajongen said:
Thank you.
What would be my region?
I purchased it in the US unlocked, but US is not a choice when it comes to region.
Would I be able to see the region the phone is from from the baseband #?
Alex
Click to expand...
Click to collapse
If your reference to the baseband version# is correct -> G900FXXU1ANCE, then the region is BTU -> check this address to download the original firmware:
https://samsung-firmware.org/downlo...agon-__/1806/BTU/G900FXXU1ANCE/G900FOXA1ANCE/
After flash via Odin, reboot and optional reinstall TWRP via Odin to use other custom Roms.
Are you sure you did everything before resuming to scratch. Personaly I would have done the following:
- back up in TWRP (at least data) + back up in google drive if you use google or titanium, (anyway save your picts, ...) if rooted, it is possible to save the file containing SMS, ... search in XDA,
- format (not wipe) !!!! WARNING THIS WILL ERASE ALL !!!!!
- clean install the ROM (lineageOS or else) + optional Gapps (I use Pico),
- reboot and restore data (as shown in 2 above)
(The Roms I use on my two KLTE by personal preference order are Havoc, DotOS, Bootleggers, Resurection Remix, MSM-Extended. I also use LineageOS.
Captain Kangaroo said:
If your reference to the baseband version# is correct -> G900FXXU1ANCE, then the region is BTU -> check this address to download the original firmware:
https://samsung-firmware.org/downlo...agon-__/1806/BTU/G900FXXU1ANCE/G900FOXA1ANCE/
After flash via Odin, reboot and optional reinstall TWRP via Odin to use other custom Roms.
Are you sure you did everything before resuming to scratch. Personaly I would have done the following:
- back up in TWRP (at least data) + back up in google drive if you use google or titanium, (anyway save your picts, ...) if rooted, it is possible to save the file containing SMS, ... search in XDA,
- format (not wipe) !!!! WARNING THIS WILL ERASE ALL !!!!!
- clean install the ROM (lineageOS or else) + optional Gapps (I use Pico),
- reboot and restore data (as shown in 2 above)
(The Roms I use on my two KLTE by personal preference order are Havoc, DotOS, Bootleggers, Resurection Remix, MSM-Extended. I also use LineageOS.
Click to expand...
Click to collapse
That site is very buggy, if I search my model and enter all the other info I get to Lollipop 5.0, if I click your link, although I am registered, it does not allow me to the link you provided, I mean I can get to it but when I try to login, it takes me back to the home page, so there is no way to get to your same link while being logged in.
How do I get do the download page it is a mystery to me.
Also, how do you know from the base band that it is BTU region?
Thank you
Alex
PS: I managed to use your link in IE, this site is stone age! Unbelievable, never seen a website like this, there are bugs everywhere.
kwajongen said:
That site is very buggy, if I search my model and enter all the other info I get to Lollipop 5.0, if I click your link, although I am registered, it does not allow me to the link you provided, I mean I can get to it but when I try to login, it takes me back to the home page, so there is no way to get to your same link while being logged in.
How do I get do the download page it is a mystery to me.
Also, how do you know from the base band that it is BTU region?
Thank you
Alex
PS: I managed to use your link in IE, this site is stone age! Unbelievable, never seen a website like this, there are bugs everywhere.
Click to expand...
Click to collapse
Men, the subject of resuming to firmware has been discussed and is described in the net literature! e.g. in XDA Q&A.
This discussion is now not a thread anymore but a dialog and I’m sure it will be closed by XDA moderator for redundancy.
The warnings given when you flash a custom Rom are clear. It also implies “before all” to backup, but also keep all materials to resume to original firmware, …. Now I cannot help anymore because you have problem with downloading the firmware.
Last advice – google baseband# - there are probably other web options or torrents
!!!!Also use the thanks button!!!!
kwajongen said:
Hi guys,
My S5 was on 6.0 and have upgraded to 9 Pie but something went wrong (or I screwed up something) and I need to re-upload the original firmware, unless you have better suggestion.
Currently, I have TWRP installed as well as Android 9, however, when I turn my S5 on, I get: Set Warranty Bit:Kernel
It stays there for 30 secs then the phone boots up and everything looks fine, it connects to wi-fi etc.
One other strange thing is that I get a message on the home screen saying: unsupported SanDisk SD Card
I tried a new one, same message.
Before I started this process, I connected the phone to my PC and copied both the Phone and the Card folders, so I am good, data wise.
Basically I was thinking to go back to the very first OS, I think 4.4.2 and then re-load Lineage 16 using TWRP.
If I read the baseband version # is: G900FXXU1ANCE
If the procedure above is correct, would you be able to provide me a link to download the firmware?
I tried all the known sites, but their speed sucks, so I thought to ask here as somebody may have a link.
I will use Odin latest version to install it.
Thank you!
Alex
Click to expand...
Click to collapse
1. Its normal to have the "Set warranty: kernel" text. As my device does too. Just simply ignore it. It won't harm your device.
2. Basically you can search websites that had official Samsung stock firmware. Search your region of your device and (IMPORTANT!) your model, in your case, is G900F. (Wow same as mine but different region, Snapdragon rocks).
3. To your network problem, I think you need to wait. There is no other option.
Thanks!
Edit: https://forum.xda-developers.com/showthread.php?t=2715487
XDA forums has one. Tip: if your region isn't there, the replies have all the filmwares you can have.
Captain Kangaroo said:
Men, the subject of resuming to firmware has been discussed and is described in the net literature! e.g. in XDA Q&A.
This discussion is now not a thread anymore but a dialog and I’m sure it will be closed by XDA moderator for redundancy.
The warnings given when you flash a custom Rom are clear. It also implies “before all” to backup, but also keep all materials to resume to original firmware, …. Now I cannot help anymore because you have problem with downloading the firmware.
Last advice – google baseband# - there are probably other web options or torrents
!!!!Also use the thanks button!!!!
Click to expand...
Click to collapse
I have downloaded the firmware and this evening I will try to upload it and see what happens.
I still I have no answer to my question: how did you figure out that my firmware is BTU?
I mean, I gave you my baseband version #: G900FXXU1ANCE and when you eventually find it in any firmware sites you are given the choice to choose among many countries, expect USA and Canada.
Since I bought the phone in the US I still wouldn't know which country the firmware is from.
Would you mind to shed some light on this?
Thank you!
Alex
OfficialJohnGL4 said:
1. Its normal to have the "Set warranty: kernel" text. As my device does too. Just simply ignore it. It won't harm your device.
Click to expand...
Click to collapse
Thank you for your feedback John.
I am not sure that message is normal, if you google it they all say it is an issue with the firmware and that you need to go back to the stock one to fix it.
Is there anyone else with lineage having that same message?
Also, when I try to format my SD Card, it gets stuck to 40% and then it goes to the homepage.
I tried also a brand new card, same story.
It gives a message but it goes away after a few secs., I believe it is a Java message, but I can try again and take a picture of it.
Thank you,
Alex
kwajongen said:
I have downloaded the firmware and this evening I will try to upload it and see what happens.
I still I have no answer to my question: how did you figure out that my firmware is BTU?
I mean, I gave you my baseband version #: G900FXXU1ANCE and when you eventually find it in any firmware sites you are given the choice to choose among many countries, expect USA and Canada.
Since I bought the phone in the US I still wouldn't know which country the firmware is from.
Would you mind to shed some light on this?
Thank you!
Alex
Click to expand...
Click to collapse
I tell you my experience:
No matter the country you bought your device. As example, I leave in France, I bought mine in Hong-Kong, but choose an international device (G900F).
Before flashing anything, I checked all information in settings and recovery.
Pict below is original out of box G900FXXU1BOC7
Recovery information after latest update G900FXXS1CQD1
It happened recently 2 times my device was stuck because encription issues – I recover by reflashing original G900FXXU1BOC7 via Odin
I personally downloaded firmware as G900F – BTU, because I check the version at each updates and this sticked to BTU ONLY.
May be the site SamMobile will be more meaningful for you, because you see Countries/Operators and updates history.
https://www.sammobile.com/samsung/galaxy-s5/firmware/SM-G900F/BTU/
For your device, you have to grab the search to find the closest original (which you have) to latest update (if you have it).
For the Kernel yellow tag at warmup, this is done when you flash TWRP. No issues since 2 years operation with that using LineageOS, Havoc, DotOS, AOSP, Bootleggers, RR, ViperOS. If you flash original firmware, it will disappear because twrp is erased and original stock recovery flashed.
kwajongen said:
Thank you for your feedback John.
I am not sure that message is normal, if you google it they all say it is an issue with the firmware and that you need to go back to the stock one to fix it.
Is there anyone else with lineage having that same message?
Also, when I try to format my SD Card, it gets stuck to 40% and then it goes to the homepage.
I tried also a brand new card, same story.
It gives a message but it goes away after a few secs., I believe it is a Java message, but I can try again and take a picture of it.
Thank you,
Alex
Click to expand...
Click to collapse
When it said that you go back to stock one to fix it. Then want if it is not stock? The message is still there. Its normal if you want to install a custom ROM other than the stock one. I reinstall the stock and install custom ROM again once. It still happened.
I don't know how to remove the text but still have a custom ROM tho.
As for the SD card message, I encountered times before. Maybe you need to format using the computer.
Captain Kangaroo said:
I tell you my experience:
No matter the country you bought your device. As example, I leave in France, I bought mine in Hong-Kong, but choose an international device (G900F).
Before flashing anything, I checked all information in settings and recovery.
Pict below is original out of box G900FXXU1BOC7
Recovery information after latest update G900FXXS1CQD1
It happened recently 2 times my device was stuck because encription issues – I recover by reflashing original G900FXXU1BOC7 via Odin
I personally downloaded firmware as G900F – BTU, because I check the version at each updates and this sticked to BTU ONLY.
May be the site SamMobile will be more meaningful for you, because you see Countries/Operators and updates history.
https://www.sammobile.com/samsung/galaxy-s5/firmware/SM-G900F/BTU/
For your device, you have to grab the search to find the closest original (which you have) to latest update (if you have it).
For the Kernel yellow tag at warmup, this is done when you flash TWRP. No issues since 2 years operation with that using LineageOS, Havoc, DotOS, AOSP, Bootleggers, RR, ViperOS. If you flash original firmware, it will disappear because twrp is erased and original stock recovery flashed.
Click to expand...
Click to collapse
When I reflash the stock ROM TWRP is still there. However no "Set warranty: kernel" appeared. Maybe its just when you install a custom ROM or something, I don't know.
OK guys,
Lineage 16 is installed, everything went smoothly, however when I connect the USB, the phone just shows as 'SM-G900F' on my W10 PC and cannot be expanded, basically no Phone and SD Card folders.
I can see them in the phone no problem, but once I connect it, I am not prompted with the usual message on what I want to do, like file transfer etc. and on the left menu appears only the model of the phone.
I had no issues when I flashed the original firmware, so it must be related to Lineage.
I also installed the Android USB drivers, but no go.
Changing the USB Preferences, to PTP or File Transfer only allows me to see the phone, no SD.
I also tried a new SD, no success.
I am stuck again... Jeez it takes days to get this stuff to work, you do one step ahead and another back
Ideas?
Alex
Anyone?
Shall I ask the question in the Lineage section?
'Set warranty :kernel' means you are running a custom kernel. Any modified boot.IMG can cause this message. It doesn't mean you need to use stock room. This appears even in stock rom with magisk or SuperSU.

Categories

Resources