Database Users

Help! IMEI=0 only 4.2.2 boots no signal

I was on stock android version 4.2.2 with stock recovery and unrooted when I received the 4.3 version notification after updating the boot animation remained stuck on the X logo for hours and clearing cache,data from stock recovery didn't help it boot. I flashed the factory 4.2.2 image and it finally booted but I had no phone signal only wifi was working. On inspection I discovered that the baseband was 'unknown' and IMEI number, IMEI SV reset to zero. Strangely the baseband was being detected while in bootloader mode. I have tried both custom recoveries, flashed various roms through custum recovery as well as stock factory images right uptil kitkat. These are my findings:
All Android 4.2.2(and 4.2.1) based roms boot but with baseband unknown and IMEI 0 rendering the phone unable to make calls and send/receive text messages.
All Android 4.3 roms don't boot are stuck at boot animation(flashing old radios like 0.48 and other older versions didn't help)
All Android 4.4 roms also behave the same way as 4.3 i.e stuck at boot animation.
Bottom line is I am stuck on Android 4.2x with a non working radio IMEI=0.... My device is now a mere tablet with inability to be updated. I have seen many people with similar problems but all such threads remain unresolved. I don't know what bug in 4.3 has done this to my phone I even tried the 99 percent working unbrick method but to no avail. I am considering selling this phone at a big loss(cant do much because I am in Pakistan) if any experienced developer is able to help me with fixing my phone(if that's even possible) then I shall be really grateful. Otherwise its bye bye Nexus 4.

liquidmetal88 said:
I was on stock android version 4.2.2 with stock recovery and unrooted when I received the 4.3 version notification after updating the boot animation remained stuck on the X logo for hours and clearing cache,data from stock recovery didn't help it boot. I flashed the factory 4.2.2 image and it finally booted but I had no phone signal only wifi was working. On inspection I discovered that the baseband was 'unknown' and IMEI number, IMEI SV reset to zero. Strangely the baseband was being detected while in bootloader mode. I have tried both custom recoveries, flashed various roms through custum recovery as well as stock factory images right uptil kitkat. These are my findings:
All Android 4.2.2(and 4.2.1) based roms boot but with baseband unknown and IMEI 0 rendering the phone unable to make calls and send/receive text messages.
All Android 4.3 roms don't boot are stuck at boot animation(flashing old radios like 0.48 and other older versions didn't help)
All Android 4.4 roms also behave the same way as 4.3 i.e stuck at boot animation.
Bottom line is I am stuck on Android 4.2x with a non working radio IMEI=0.... My device is now a mere tablet with inability to be updated. I have seen many people with similar problems but all such threads remain unresolved. I don't know what bug in 4.3 has done this to my phone I even tried the 99 percent working unbrick method but to no avail. I am considering selling this phone at a big loss(cant do much because I am in Pakistan) if any experienced developer is able to help me with fixing my phone(if that's even possible) then I shall be really grateful. Otherwise its bye bye Nexus 4.
Click to expand...
Click to collapse
try this for reference http://blog.falcondai.com/2013/10/fixing-galaxy-nexuss-imei-number.html

But this post specifically required the IMEI number to be exactly the SAME as mentioned otherwise it says the method wont work and it also seems to be T-Mobile blocked IMEI or something I don't think this fix is for my issue(correct me if I am wrong I am a noob lol)
My IMEI issue seems to linked to the Android 4.3 update which has broken something and this problem seems quite common on Nexus 4 as I came across many threads with people with exactly the same issue as mine. All the replies given usually say wipe cache and/or flash factory image sadly the problem remains.
I am really disappointed at my decision to buy the Nexus 4(my year long experience with the Galaxy Nexus was without issues) I never expected Google to release an update that breaks radios of many users(just google this problem many seem to have exactly the same symptoms as mine but the problem remained unresolved) and then remain silent despite many complaining on their product support forums.
Seems the device is beyond repair like most affected Nexus 4 phones(some have luckily got fixed by themselves it seems and IMEI appeared again)
Guess I will have to sell it at a very low price. I am skeptical about buying even the Nexus 5 now should I run into another dreaded unfixable IMEI issue caused by Google's own update(just paranoia I guess)
If only someone comes up with some fix I guess that will help plenty of disappointed Nexus 4 owners.

liquidmetal88 said:
But this post specifically required the IMEI number to be exactly the SAME as mentioned otherwise it says the method wont work and it also seems to be T-Mobile blocked IMEI or something I don't think this fix is for my issue(correct me if I am wrong I am a noob lol)
My IMEI issue seems to linked to the Android 4.3 update which has broken something and this problem seems quite common on Nexus 4 as I came across many threads with people with exactly the same issue as mine. All the replies given usually say wipe cache and/or flash factory image sadly the problem remains.
I am really disappointed at my decision to buy the Nexus 4(my year long experience with the Galaxy Nexus was without issues) I never expected Google to release an update that breaks radios of many users(just google this problem many seem to have exactly the same symptoms as mine but the problem remained unresolved) and then remain silent despite many complaining on their product support forums.
Seems the device is beyond repair like most affected Nexus 4 phones(some have luckily got fixed by themselves it seems and IMEI appeared again)
Guess I will have to sell it at a very low price. I am skeptical about buying even the Nexus 5 now should I run into another dreaded unfixable IMEI issue caused by Google's own update(just paranoia I guess)
If only someone comes up with some fix I guess that will help plenty of disappointed Nexus 4 owners.
Click to expand...
Click to collapse
Your IMEI information should be on your box if you still have it. Now there has to be a tutorial out there somewhere to enter IMEI info for your phone. I know I found some stuff when trying to this to a Galaxy S3.... I would keep looking or contact Google for a RMA

Still no luck. Now flashing the just released Kitkat image, who knows it may work.
Edit: Still the same result.
Wonder why only 4.2.2 based roms boot but 4.3x and 4.4 based ones do not. I also don't get why baseband is detected in the bootloader mode but not within the OS.
And what is the process of this RMA thingy? Is it applicable for countries outside US? I am from Pakistan btw and got it from a local shop. Nexus 4 can't be bought from Play Store in my country

Any Luck yet?
liquidmetal88 said:
Still no luck. Now flashing the just released Kitkat image, who knows it may work.
Edit: Still the same result.
Wonder why only 4.2.2 based roms boot but 4.3x and 4.4 based ones do not. I also don't get why baseband is detected in the bootloader mode but not within the OS.
And what is the process of this RMA thingy? Is it applicable for countries outside US? I am from Pakistan btw and got it from a local shop. Nexus 4 can't be bought from Play Store in my country
Click to expand...
Click to collapse
Hi @[liquidmetal88] did you get any solution, exactly the same issue as yours. Please share if you have solved it, would be of great help

sambitshankar said:
Hi @[liquidmetal88] did you get any solution, exactly the same issue as yours. Please share if you have solved it, would be of great help
Click to expand...
Click to collapse
Am also facing this issue...only the 4.2.2 boots with no basebanc versiono no IMEI no. and doesn't detects any Sim card

Unlike Samsung phones, the imei cannot be re-injected into the phone's file system. People have had to return the phone to Google to have it fixed.
If you try to install a stock 4.3 or 4.4 ROM, the phone will not even boot to the desktop.

Sigh.. Bootloop problem out of nowhere

My Nexus 6p was definitely one of the batches that should not have passed QC... soft power button, phone shutting down with plenty of battery left and today all of a sudden, while I was using the phone, phone restarts and get stuck in a bootloop...
Phone is not rooted and the bootloader locked... its out of warranty but I called google support anyway and they directed me to Huawei .. luckily, they will fix it for free..
IF you are having the same problem, call google up and hold them accountable for this bull****

Same deal here but i bought my 6p from best buy along with geek squad protection plan. Rather than send me another 64gb 6p, they've given me a gift card for the price at the time of purchase. At the moment only 32gb versions are available on best buy dot com. I'm not totally opposed to the 32gb version but I'm not excited about it. It took 3 days from the time I submitted my RMA request to get an email telling me this gift card b.s.
I haven't returned anything yet. Not sure what to do. I really liked that phone.

i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps.
phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)

puddi said:
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps. phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
Click to expand...
Click to collapse
I wouldn't be. Sounds like you are unlocked and rooted. Just keep a good backup on your PC (including EFS) and enjoy your phone.

puddi said:
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps.
phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
Click to expand...
Click to collapse
Rooted or not and having a backup or not won't fix this unfixable bootloop. I have one in my possession I'm trying to restore and nothings working. Random reboots a week prior to it going into this bootloop. I've done a bunch of research and it's not good.

thesparky007 said:
My Nexus 6p was definitely one of the batches that should not have passed QC... soft power button, phone shutting down with plenty of battery left and today all of a sudden, while I was using the phone, phone restarts and get stuck in a bootloop...
Phone is not rooted and the bootloader locked... its out of warranty but I called google support anyway and they directed me to Huawei .. luckily, they will fix it for free..
IF you are having the same problem, call google up and hold them accountable for this bull****
Click to expand...
Click to collapse
Do you have the Huawei contact info? I have tried to go through the online support but I have yet to hear anything in a number of days. Same problem here, bootloop out of no where.

galakanokis said:
Do you have the Huawei contact info? I have tried to go through the online support but I have yet to hear anything in a number of days. Same problem here, bootloop out of no where.
Click to expand...
Click to collapse
Call them here 1-888-5HUAWEI

thesparky007 said:
Call them here 1-888-5HUAWEI
Click to expand...
Click to collapse
Thanks, much appreciated.

I just went through the same thing. Waiting on the RMA box to arrive so it can be sent back.
Sent from my Nexus 6 using XDA-Developers Legacy app

Same here...happened just this morning. I can't get into recovery and I can ONLY boot into bootloader. I am on full stock with a locked bootloader running 7.1.1. I got off the phone with a Huawei rep and she stated it could be due to a Google update and that they will try and downgrade it on their end. Strange cause I was already running the latest 7.1.1 (unless a new update was released his morning).
Here's what I tried to no avail:
-unlocked bootloader and tried to flash stock rom/recovery
-tried flashing custom recovery (twrp)
-tried booting into temp customer recovery (twrp)
-tried flashing 7.0 stock
I have re-locked the bootloader and will have to send it in. What a real bummer, I have managed to get out of a softbrick (unless this device is truly bricked ???) on many, many device since the T-Mobile G1, but I am at wits end with this device.

Going through the RMA process now, thanks again for the number.
I have heard it mentioned that flashing back to 6.0.1 might work, has anyone tried? I did flash all the way back to 7.0 with no luck.

tried flashing back to 6, 6.01 and 7.0 but it still persists. get it exchanged or repaired

It's now several phones a day... At what point does either Huawei or Google fess up to root cause? The one question I have is are all of these hard bricks on phones running nougat??
Sent from my Nexus 6 using XDA-Developers Legacy app

uzi132 said:
Same here...happened just this morning. I can't get into recovery and I can ONLY boot into bootloader. I am on full stock with a locked bootloader running 7.1.1. I got off the phone with a Huawei rep and she stated it could be due to a Google update and that they will try and downgrade it on their end. Strange cause I was already running the latest 7.1.1 (unless a new update was released his morning).
Here's what I tried to no avail:
-unlocked bootloader and tried to flash stock rom/recovery
-tried flashing custom recovery (twrp)
-tried booting into temp customer recovery (twrp)
-tried flashing 7.0 stock
I have re-locked the bootloader and will have to send it in. What a real bummer, I have managed to get out of a softbrick (unless this device is truly bricked ???) on many, many device since the T-Mobile G1, but I am at wits end with this device.
Click to expand...
Click to collapse
You aren't alone obviously. These phones seem to be little time bombs where the boot loop issue is concerned. Mine goes into bootloops every time I flash an update or new ROM or attempt to restore a backup. I expect to hardbrick this phone at some point. It just hasn't happened yet.

Completely forgot about this thread. Huawei swapped out my motherboard with a 128 Gb (I had sent a 64 Gb). I actually quite happy my phone bricked itself. Haha

My 6p started rebooting last night and no matter what I did, couldn't get it to boot. Only bl mode worked. This thing has been one problem after another, so I went and got an iPhone this morning. Maybe one day Google will finally start making products that last more than one year, but hasn't happened yet and I'm tired of it.

andrewnelson23 said:
My 6p started rebooting last night and no matter what I did, couldn't get it to boot. Only bl mode worked. This thing has been one problem after another, so I went and got an iPhone this morning. Maybe one day Google will finally start making products that last more than one year, but hasn't happened yet and I'm tired of it.
Click to expand...
Click to collapse
On the same boat. Mine's stuck on bootloop, no recovery. 1 year is pretty good considering I've only had the device for 3 months...

Nexus 6p here in the UK, Got the OTA update yesterday and it caused crashes immediately. Had two crashes when it immediately rebooted and seemed ok. A third one soon followed and got stuck in a boot loop, a few minutes after it fixed it self and seemingly working fine. An hour later i was playing a game and it just locked, screenfroze and a buzzing noise from the speakers before going into a boot loop. Left it for a few hours while at the cinema and nothing.
Bought directly from Google and still under warranty. Interestingly though, i bought my 6p in March 2016, I then had to RMA it a few months later as the USB C port randomly broke I will be doing my second RMA in less than a year. When checking my IMEI the google support operative actually stated I was under warranty till August 2018. So a 30 month warranty. Got a new one coming out so if anyone develops this problem give them a ring.

New phone received, sent old one off. Checked it just before i did, still stuck in boot loop.

Narom88 said:
New phone received, sent old one off. Checked it just before i did, still stuck in boot loop.
Click to expand...
Click to collapse
That's way too common with this phone. Thinking about moving on to something else.

After 7.1.2 update, no service, no SIM detected, no IMEI, no band base

Hi everyone,
Google messed up ! I received the OTA for the 7.1.2 uptdate last thursday. After it my phone was unable to detect my SIM card, my IMEI number disappeared, neither base band.
The first thing i've tried is to get a new SIM card, with no result, then I tried a soft reset, an hard reset (factory reset+wipe data), and wiping the cache without any positive result either. I've contacted Google, the phone was from Google Store and my 1 year warranty expired on 25/03/17 (the update was installed on 05/04/17, exactly two week later), they refused to take it back, nor RMA, a shame! I think it will be the last Google phone I buy!
I've tried to flash the full factory image of 7.1.1. but nothing positive from it. I think the OTA corrupted my EFS data files but no idea on how to fix it. The thing is when i'm going to the bootloader, under barcodes menu i still find an IMEI number.
I don't know what to do now, I'm little bit desperate, if anyone have an advice here.:crying::crying:
Thank you in advance.
Nexus 6P
7.1.2 build N2G47H
kernel 3 .10.73-g0a21e4c
Bootloader locked
Unrooted

blckhwkone said:
Hi everyone,
Google messed up ! I received the OTA for the 7.1.2 uptdate last thursday. After it my phone was unable to detect my SIM card, my IMEI number disappeared, neither base band.
The first thing i've tried is to get a new SIM card, with no result, then I tried a soft reset, an hard reset (factory reset+wipe data), and wiping the cache without any positive result either. I've contacted Google, the phone was from Google Store and my 1 year warranty expired on 25/03/17 (the update was installed on 05/04/17, exactly two week later), they refused to take it back, nor RMA, a shame! I think it will be the last Google phone I buy!
I've tried to flash the full factory image of 7.1.1. but nothing positive from it. I think the OTA corrupted my EFS data files but no idea on how to fix it. The thing is when i'm going to the bootloader, under barcodes menu i still find an IMEI number.
I don't know what to do now, I'm little bit desperate, if anyone have an advice here.:crying::crying:
Thank you in advance.
Nexus 6P
7.1.2 build N2G47H
kernel 3 .10.73-g0a21e4c
Bootloader locked
Unrooted
Click to expand...
Click to collapse
Hello...
Unless you have a TWRP EFS backup, there's not much you can do...
I already saw some people saying that a restore from someone else EFS backup solved the problem and their proper IMEI, etc were back. I never had the issue, so I can't confirm it really works.
Now you need to find someone who can give it to you.
Otherwise you can RMA...
Good luck...

Is there any personal info in the efs backup? I would be happy to help but am not going to jeopardize privacy...
Sent from my Nexus 6 using XDA-Developers Legacy app

CyberpodS2 said:
Is there any personal info in the efs backup? I would be happy to help but am not going to jeopardize privacy...
Click to expand...
Click to collapse
Hello...
Since his IMEI disappeared, there must be infos about it somewhere in the EFS. I don't know what else...
Cheers...

CyberpodS2 said:
Is there any personal info in the efs backup? I would be happy to help but am not going to jeopardize privacy...
Click to expand...
Click to collapse
I think giving someone a copy of your efs partition essentially gives them the information needed to clone your phone, so it's not something you would want to do for a stranger.

blckhwkone said:
Hi everyone,
Google messed up ! I received the OTA for the 7.1.2 uptdate last thursday. After it my phone was unable to detect my SIM card, my IMEI number disappeared, neither base band.
The first thing i've tried is to get a new SIM card, with no result, then I tried a soft reset, an hard reset (factory reset+wipe data), and wiping the cache without any positive result either. I've contacted Google, the phone was from Google Store and my 1 year warranty expired on 25/03/17 (the update was installed on 05/04/17, exactly two week later), they refused to take it back, nor RMA, a shame! I think it will be the last Google phone I buy!
I've tried to flash the full factory image of 7.1.1. but nothing positive from it. I think the OTA corrupted my EFS data files but no idea on how to fix it. The thing is when i'm going to the bootloader, under barcodes menu i still find an IMEI number.
I don't know what to do now, I'm little bit desperate, if anyone have an advice here.:crying::crying:
Thank you in advance.
Nexus 6P
7.1.2 build N2G47H
kernel 3 .10.73-g0a21e4c
Bootloader locked
Unrooted
Click to expand...
Click to collapse
Google's been messing up along recently

blckhwkone said:
Google messed up !
Click to expand...
Click to collapse
Several people have been able to recover from this by wiping both the EFS partitions, but because your bootloader is locked (and USB debugging probably not enabled), I don't believe there is any way forward. See the link for the method used: http://www.theandroidsoul.com/fix-e...d-wifibluetooth-issues-restoring-twrp-backup/

Mi a1 no network signal - please help!!!!!

Hi Devs and team,
I have no network signal (AIRTEL or IDEA) in India. (Possibly due to PIE update) No 4g, 3g or even 2g.
I will briefly explain what happened:
1. I was in Oreo November patch till 1st week of Jan 2019 and i was not upgrading to PIE update Jan patch as well, due to all the discussion on bugs and all.
2. However, one day around 8 or 9 Jan, i noticed that update has been downloaded onto my device and it was asking for a reboot to install.
3. But i was avoiding that restart as well since i was scared i would be affected by bugs.
4. Suddenly, around 13 or 14 Jan , i lost mobile signal just like that. (NOTE THAT I DID NOT RESTART MY PHONE YET)
5. I still left my phone like that for a day and there was no change in network signal. Then i thought this may be xiaomi's way of forcing me to install the pie update and then i restarted and PIE was installed.
6. But still there was no signal. Even then i waited for 1-2 days and thought that this may get resolved.
7. Finally around 16 Jan, as my phone was still not getting any signal, i went on the internet trying to search for solutions.
8. I did everything possible. DOWNGRADED from Pie to Oreo 8.0, 8.1, Nougat (Aug 2017 build), used fastboot for this process and then used even hotboot twrp for this process, rooted, then unrooted. I have done this countless times. (Maybe 10-15 times, tried various combinations) Please note that i never had any problem with my IMEI. I always had my IMEI intact during this process. But i never had my signal back. I flashed only modem firmware as well just in case. I am still searching for answers.
9. Meanwhile, i took my phone to Xiaomi service center and after checking they just said, i had to replace my Motherboard and it would cost around 8k (approx). Mind that i bought this phone for 13k. I refused and i thought i would get it checked outside.
10. I took my phone to unauthorised service center as well. Even before diagnosing my phone, he said either antenna or network IC may have been faulty. It has been 2 days and he is now saying he is not able to point out what the problem is yet.
11. It has been more than 20 days and i am without a phone. Everything else works on my phone except for the network signal.
PLEASE HELP ME. I am not able to figure out whether its a software problem or hardware.
I have read that many users have problems with signal. can someone tell me what to do.
My opinion is that maybe seamless update feature helped whatever bug is there in pie to affect my device in oreo and now, i have no signal now whatever i do.
UPDATE: I have just checked with the service center guy (unauthorised) - he says he tried everything (including replacing antenna and other stuff) except for changing network IC. He says changing network IC is risky and it may damage other components. I am not able to decide what to do.

How did you downgrade to Oreo from Pie. As of stock pie for this device, there is arb which will cause bootloops if you downgrade with the usual methods. The steps to downgrade is now more difficult.

I'm no expert, but given what you describe and what Service Center told you, it looks more like Hardware issue than anything else.
If it was software, with all the downgrades you did, you should have been able to get back to a situation where it worked. One thing though, did you try it with another SIM/Operator? SIMs can die too, and usually your operator should give you a new SIM for free or cheap, and you could as well borrow a SIM from someone else, to confirm it's really the full phone that is dead.
So your phone is most likely broken... I guess that if Service Center said you have to pay for motherboard replacement that you are out of your warranty period? Because if you're still under warranty, they should replace for free...

You sure your Sim isn't broken?

Yes to all your questions.
1) i have tried my sims in other phones (they work) and Other sims in my phone (they dont work). Tried hard reset, soft rest etc., nothing works.
2) I have downgraded as per the tutorial of downgrade in xda forums. i had no bootloop or no imei lost cases. Everytime my phone booted well with all imei's intact. I went from oreo 8.0 to pie (over OTA again after proper downgrade) and pie to oreo 8.0 oreo 8.1 nougat.
As i said, i have tried all combinations.
Request your help.

Try installing any custom rom

Can you suggest one so that i can try? Also please tell me rooting from which version would be better. Nougat or Oreo 8.1? I would prefer one which would solve my issue.
FYI: That service centre guy returned my device, saying he could not repair it.
Apart from the above, i have a doubt whether reinstalling my IMEI may kick my modem to start picking up a signal. can i do that? Can i rewrite the same IMEI again?

Str!der said:
Can you suggest one so that i can try? Also please tell me rooting from which version would be better. Nougat or Oreo 8.1? I would prefer one which would solve my issue.
FYI: That service centre guy returned my device, saying he could not repair it.
Apart from the above, i have a doubt whether reinstalling my IMEI may kick my modem to start picking up a signal. can i do that? Can i rewrite the same IMEI again?
Click to expand...
Click to collapse
U can try pie based roms like Los16 , PE latest , crdroid ,etc they r stable for daily driver.
Rooting from 8.1 would be better
Don't touch IMEI for now , try installing custom ROM , if network works then stick to custom ROM and if it doesn't work then it would be a hardware issue.

Have you checked your APN, I lost mine after an update, I manually re entered all the details and all was perfect again.

Did u got your network issue solved?
I'm facing the same issue . .

I need help, my wifi not work

I have had a moto g6 plus for some time now, but nowadays I am not able to detect SIM cards and wifi does not turn on, what is happening?

Wellfare11 said:
I have had a moto g6 plus for some time now, but nowadays I am not able to detect SIM cards and wifi does not turn on, what is happening?
Click to expand...
Click to collapse
Can you tell us more?
How did it start?
Did something happen to it, or did you just notice it is not connecting?
The most easy things first, is your sim card correctly in place?
Which ROM are you on and have you reflashed it?

weazie said:
Can you tell us more?
How did it start?
Did something happen to it, or did you just notice it is not connecting?
The most easy things first, is your sim card correctly in place?
Which ROM are you on and have you reflashed it?
Click to expand...
Click to collapse
The phone started with problems since I upgraded to Android Pie, I have taken care of it very well but I do not know if it is a hardware failure, but note that in baseband turns out to be unknown, I installed several stock roms from fastboot without any success, also I thought it would be a problem of the EFS partition, but everything is fine I even took a backup in case the doubts, what could happen?

Wellfare11 said:
The phone started with problems since I upgraded to Android Pie, I have taken care of it very well but I do not know if it is a hardware failure, but note that in baseband turns out to be unknown, I installed several stock roms from fastboot without any success, also I thought it would be a problem of the EFS partition, but everything is fine I even took a backup in case the doubts, what could happen?
Click to expand...
Click to collapse
Did you originally update via OTA, meaning, was it the official update?
Then when you noticed it's not working, you tried to flash several stock ROMs?
One possible problem that comes to mind, is that for some reason, you have the wrong radio/modem firmware. That can happen for example, if you have flashed a ROM, which is not meant for your region.

weazie said:
Did you originally update via OTA, meaning, was it the official update?
Then when you noticed it's not working, you tried to flash several stock ROMs?
One possible problem that comes to mind, is that for some reason, you have the wrong radio/modem firmware. That can happen for example, if you have flashed a ROM, which is not meant for your region.
Click to expand...
Click to collapse
Yes, upgrade to Android pie via OTA
I already put a stock rom of the same region, following each fastboot command one by one, but everything continues the same, I even installed RROS 7, to see if at least it turned on the wifi, and it is in bootloop.

Wellfare11 said:
Yes, upgrade to Android pie via OTA
I already put a stock rom of the same region, following each fastboot command one by one, but everything continues the same, I even installed RROS 7, to see if at least it turned on the wifi, and it is in bootloop.
Click to expand...
Click to collapse
Go with the modding guide index: how to restore stock ROM etc., and flash a stock ROM that you know will work. Flash the radio/modem file too, and make sure it's the correct one.
Just to say, I had connection problems too, and in the end they were because the sim card did not latch correctly in place i.e. was not correctly in place.

weazie said:
Go with the modding guide index: how to restore stock ROM etc., and flash a stock ROM that you know will work. Flash the radio/modem file too, and make sure it's the correct one.
Just to say, I had connection problems too, and in the end they were because the sim card did not latch correctly in place i.e. was not correctly in place.
Click to expand...
Click to collapse
I already tried, I installed the rom corresponding to the model of the cell phone and the wifi still does not work, the base band is still unknown, I also checked if the sim card was correctly placed, and everything is fine

weazie said:
Go with the modding guide index: how to restore stock ROM etc., and flash a stock ROM that you know will work. Flash the radio/modem file too, and make sure it's the correct one.
Just to say, I had connection problems too, and in the end they were because the sim card did not latch correctly in place i.e. was not correctly in place.
Click to expand...
Click to collapse
I have an idea, but I need someone to help with a backup of the files, Radio, Modem, and Persist to flash in twrp

Wellfare11 said:
I have an idea, but I need someone to help with a backup of the files, Radio, Modem, and Persist to flash in twrp
Click to expand...
Click to collapse
Great that you have an idea. ?
Here's an idea: take a backup of your current config in twrp, move it to the computer, take a copy. Replace the files in that copy with the ones that you want to flash.
Did you mean this? You are aware that you can try different radio/modem files through fastboot, not having to flash everything else every time? That said, go with your idea. ?

weazie said:
Great that you have an idea.
Here's an idea: take a backup of your current config in twrp, move it to the computer, take a copy. Replace the files in that copy with the ones that you want to flash.
Did you mean this? You are aware that you can try different radio/modem files through fastboot, not having to flash everything else every time? That said, go with your idea.
Click to expand...
Click to collapse
I already tried and still does not give results curiously I have noticed that even in bootloader shows, Baseband not fund

Wellfare11 said:
I already tried and still does not give results curiously I have noticed that even in bootloader shows, Baseband not fund
Click to expand...
Click to collapse
Does the phone ask for a pin code at any point?

weazie said:
Does the phone ask for a pin code at any point?
Click to expand...
Click to collapse
does not request any code at any time

Wellfare11 said:
does not request any code at any time
Click to expand...
Click to collapse
Ok, but WiFi should work even if there is no mobile data available.
I probably can't help at this point, apologies! My suggestion is to flash a stock ROM, lock the bootloader and send the phone for repairs. There could be a solution to this, but I'm out of ideas. ?*

weazie said:
Ok, but WiFi should work even if there is no mobile data available.
I probably can't help at this point, apologies! My suggestion is to flash a stock ROM, lock the bootloader and send the phone for repairs. There could be a solution to this, but I'm out of ideas. *
Click to expand...
Click to collapse
from what I see, if there is no baseband it does not detect the sim card and it does not turn on the wifi, I will try to force an OTA retail update
it did not work

Wellfare11 said:
from what I see, if there is no baseband it does not detect the sim card and it does not turn on the wifi, I will try to force an OTA retail update
it did not work
Click to expand...
Click to collapse
Hello, colud you solve the problem? Because I am havig a very similar one...

Hello group friends, I'm new here. I have a similar problem, I was using the Havoc 2.4 rom, when upgrading to 2.6 I no longer recognize my SIM card and the wi-fi does not connect, I can not install another rom anymore, nor rom stock, recovery TRWP has been replaced by the Havoc and the Wipe System function does not work, and for a few days you can not stay in recovery mode anymore, it restarts every 3 seconds, not the time to click the options. Can someone help me. I'm without a cell phone, and I need it.

I have a similar issue after flashing the latest firmware. SIM goes to "SIM locked" every ten seconds or so, and Wifi drops at the same tie. It's like networking is being reset every 10 seconds. No network settings I've tried change that.
I've flashed several stock ROMs; the one I had previously, newest, oldest, both for RETEU and retail. I used Lenovo restore to upgrade but that resulted in soft brick, after that I flashed the latest firmware via Fastboot and that's when the problem started.
With Oreo, wifi and cellular don't work at all, nothing detected. With Pie they're connected and dropped in a loop. I can't help thinking that the Lenovo restore broke this somehow, but modem files have been reflashed several times after that with no change. I'm not getting the baseband error.

bitstuff said:
I have a similar issue after flashing the latest firmware. SIM goes to "SIM locked" every ten seconds or so, and Wifi drops at the same tie. It's like networking is being reset every 10 seconds. No network settings I've tried change that.
I've flashed several stock ROMs; the one I had previously, newest, oldest, both for RETEU and retail. I used Lenovo restore to upgrade but that resulted in soft brick, after that I flashed the latest firmware via Fastboot and that's when the problem started.
With Oreo, wifi and cellular don't work at all, nothing detected. With Pie they're connected and dropped in a loop. I can't help thinking that the Lenovo restore broke this somehow, but modem files have been reflashed several times after that with no change. I'm not getting the baseband error.
Click to expand...
Click to collapse
I have the exact same problem, I wasn't able to repair it so I sent it to service and tomorrow they will try to fix it for $35. The problem with goign back to previous versions is that you loose the IMEI and MAC . The problem with the pie version I believe is the baseband. If the service is able to fix it I will post the solution here for you to fix it .

bitstuff said:
I have a similar issue after flashing the latest firmware. SIM goes to "SIM locked" every ten seconds or so, and Wifi drops at the same tie. It's like networking is being reset every 10 seconds. No network settings I've tried change that.
I've flashed several stock ROMs; the one I had previously, newest, oldest, both for RETEU and retail. I used Lenovo restore to upgrade but that resulted in soft brick, after that I flashed the latest firmware via Fastboot and that's when the problem started.
With Oreo, wifi and cellular don't work at all, nothing detected. With Pie they're connected and dropped in a loop. I can't help thinking that the Lenovo restore broke this somehow, but modem files have been reflashed several times after that with no change. I'm not getting the baseband error.
Click to expand...
Click to collapse
Service couldn't fix it. Being honest they were quite incompetent, when I explained the problem he said "we should hire you" ( I am 16 years old) . Anyway, could you fix it? Because I am not even close
---------- Post added at 03:00 AM ---------- Previous post was at 02:54 AM ----------
caradobeco said:
Hello group friends, I'm new here. I have a similar problem, I was using the Havoc 2.4 rom, when upgrading to 2.6 I no longer recognize my SIM card and the wi-fi does not connect, I can not install another rom anymore, nor rom stock, recovery TRWP has been replaced by the Havoc and the Wipe System function does not work, and for a few days you can not stay in recovery mode anymore, it restarts every 3 seconds, not the time to click the options. Can someone help me. I'm without a cell phone, and I need it.
Click to expand...
Click to collapse
Sorry I answer so late, I didn's see the message before.
I believe you already tried puting it into bootloader mode. If that's the case, I had a similar problem recently an it solved alone, I let it loop for a while and suddenly fell, into dtock recovey, i factory reset (with stock recovery) and somehow stock was booted ( i believe it was because it was in inactive slot).
Hope this helps you

juampapo546 said:
Service couldn't fix it. Being honest they were quite incompetent, when I explained the problem he said "we should hire you" ( I am 16 years old) . Anyway, could you fix it? Because I am not even close
---------- Post added at 03:00 AM ---------- Previous post was at 02:54 AM ----------
Sorry I answer so late, I didn's see the message before.
I believe you already tried puting it into bootloader mode. If that's the case, I had a similar problem recently an it solved alone, I let it loop for a while and suddenly fell, into dtock recovey, i factory reset (with stock recovery) and somehow stock was booted ( i believe it was because it was in inactive slot).
Hope this helps you
Click to expand...
Click to collapse
I am still working on this, I actually did this to a work phone (I had permission to root/unroot). Something that has helped me so far is just getting familiar with the whole flashing process - https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/. I think from this article the problem lies in the modem/radio rom. That *should* be the only thing you need to flash on. However, I have noticed with a lot of roms on here, a modem rom is not included on the stock firmware. But that needs to match well to your phone from what I understand. I have tried a few modem roms already, unfortunately, but no luck.