Related
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Seriously???
pastorbob62 said:
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Click to expand...
Click to collapse
Not to be negative or anything but I think this is the least responsive forum on this site. I have spent hours searching for possible solutions to various problems I've encountered over the past several months, asked several questions and received little if any help. I was only able to get back from a bricked phone to where I am now by using information found on other websites. Pretty sad if you ask me.
In contrast, whenever I have asked a question on my tablet's forum I've received fast workable solutions/answers to my problems/queries. The threads are informative, well organized and contain answers to any situation I have encountered.
Granted, my current problem with my phone is my own fault for trying to customize it. And I suspect part of the problem is due to the age of this phone thus most of the "experts" have moved on to other ventures. It is also hindered by the lack of information available from Huawei and the service providers.
All of that said, if anybody has any suggestions for how I can repair the ESF partition or whatever is causing this lack of mobile service issue I would be extremely grateful. It isn't the end of the world since i have a new phone (Consumer Cellular) that I am currently using but it would be great to get this one working since it's much faster and more streamlined than my stock Consumer Cellular version.
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
Thank you very much for your reply. It seems that you have found the answer to my problem. But unfortunately, I don't have a copy of the original stock ROM. My phone is the -51 version and any links I have found to the stock ROM are broken. There is a version I found but it is for Venezuela and I don't think it will work. I am leery to try it and totally brick my phone. My backup is apparently corrupted. I backed up my new working phone with Disk Image and attempted to restore it to the broken phone but all that did was cause it to come up to the ATT logo screen for a few seconds and then shut down. It wouldn't do anymore than that. So I restored the Stallion 3.5 image I made and am back to a great fast tablet with no phone service. I also tried backing up my IMEI on the working phone and restoring it to the broken phone but that had no effect.
It is my understanding that the -Pro version of the ROM will work, but I don't have the stock image of that either. I suspect it work might since I was able to use the -Pro version of GB on it. All of my internet searches have only turned up custom ROMs and other desperate people looking for fixes for similar problems or worse. I agree 100% with your assessment of Huawei's lack of meaningful support. It really is a shame, because these phones aren't half bad when they have been customized and OC'ed a little.
I have just about given up on it and resigned myself to using it as an MP3 player for my car system. I have learned my lesson and am leaving the working phone stock. It is rooted and I have cleaned off all of the bloatware, and set it up so most apps run from my SD card, so it really isn't half bad. At least it works.
Again, thank you for your reply and advice.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
ggunzio said:
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
Click to expand...
Click to collapse
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Blefish said:
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Click to expand...
Click to collapse
i have exactly the same phone than you, because i installed that backup too. After installed it, the IMEI SV is 36, after installing B518 it says it is 18, but before it was 17, and i had 3g signal, but not now.
My question is, wich SV is your phone reporting?
Thank you
I also have a problem like this, but I think it's a bit more severe. My phone got stuck while charging. Couldn't reboot. Was getting stuck on the aurora loading screen(using DZO 5u20). Than reinstalled whole rom. But now I don't any signal and the phone doesn't even see a SIM card. Showing 'baseband unknown' and the IMEI and IMEI SV are also unknown. Not 0's but just unknown. Is this is a similar problem? And can something be done to fix it.
I had some backups on my sd card, untill the sd-card got fried in the phone a couple of months ago.
I was trying to root my at&t s6 edge+ using Odin. As soon as the process completed, my phone froze on Samsung screen. Then I tried wiping cache and data but nothing worked. I downloaded few stock ROM for Odin but flashing keeps on failing. I read in some thread that new Samsung devices do not support downgrading. I went and checked my current build number and found that to be G928AUCS4CPK1. However, the firmware I was trying to flash were older version.
Has anyone experienced similar issue before? The main problem here is I cannot find the exact build number anywhere. I spent a lot of time searching and finally decided to post here.
Your valuable suggestions will be greatly appreciated.
Thanks.
hey man, you flashed an older version of the firmware? even if it wasnt bricked, your phone is essentially useless now. the efs is gone, meaning you cant make phonecalls or connect to wifi at all. sorry; your phone is bricked. perm.
download mode dosen`t work ?if so the only thing you can try is to use samsung kies to restore your phone but don`t know if that works
I done something similar to my standard S6 Edge the only difference was i was able to start it up ok and i thought everything was ok until i realised i had no reception. I so happened to notice my imei number was gone. I had no back ups of the partition that saved this info so i totally bricked my phone.
I did however find a website that would be able to do a work around ( for a fee of course) for it however it does question your morals as its essentially illegal in alot of countries. I dont want to post anything on here so if you want any info send me a PM.
Exact same thing happened to me... went to AT&T repair center but they didn't have the 'K1' firmware..
anyhow managed to find the latest firmware (gsm-firmware.com)... cost me $4, but the phone is up and running... I only flashed the AP file.. also used Odin 3.12.5..
Hey guys!
After few days trying to fix the problem on my Nexus 6P, I still can't make it run properly so I decide to create a new thread asking you guys and this is my last hope for it. I had been using stock android 6.0.1 until I decided to upgrade to OTA 7.1.1 because I hate the notification on the statusbar. My phone worked fine, everything was OK on 6.0.1. After upgrading to android 7.1.1, my phone couldn't get any mobile signal. It still can detect the simcard, the sim toolkit app still shows but I can't use the network. Everything else works properly just like before upgrading. I tried to flash stock 7.1.2 n2g47o image from google; some custom roms like chroma, pure nexus, ressurection remix, flyme, ... and also tried to select automatic band but it is still the same. When I select automatic or any other band, it shows "select [band] unsuccessful". The service state shows "radio off" and I can't turn it back on in *#*#4636#*#*. Please help me! Thank you guys a lot.
tbmoc96 said:
Hey guys!
After few days trying to fix the problem on my Nexus 6P, I still can't make it run properly so I decide to create a new thread asking you guys and this is my last hope for it. I had been using stock android 6.0.1 until I decided to upgrade to OTA 7.1.1 because I hate the notification on the statusbar. My phone worked fine, everything was OK on 6.0.1. After upgrading to android 7.1.1, my phone couldn't get any mobile signal. It still can detect the simcard, the sim toolkit app still shows but I can't use the network. Everything else works properly just like before upgrading. I tried to flash stock 7.1.2 n2g47o image from google; some custom roms like chroma, pure nexus, ressurection remix, flyme, ... and also tried to select automatic band but it is still the same. When I select automatic or any other band, it shows "select [band] unsuccessful". The service state shows "radio off" and I can't turn it back on in *#*#4636#*#*. Please help me! Thank you guys a lot.
Click to expand...
Click to collapse
Try the flash all bat with stock rom and then relock your boot loader
Sent from my Pixel XL using Tapatalk
Are you with verizon, 7.1.1 has images for verizon only and except, may flashing one of those will fix your issue and use the flash all bat to wipe completely your phone.
bennyboy2120 said:
Try the flash all bat with stock rom and then relock your boot loader
Click to expand...
Click to collapse
coremania said:
Are you with verizon, 7.1.1 has images for verizon only and except, may flashing one of those will fix your issue and use the flash all bat to wipe completely your phone.
Click to expand...
Click to collapse
Thank you guys and sorry for not saying, I flashed both 7.1.1 (NUF26N, Mar 2017, Verizon Only) and 7.1.2 (N2G47O, May 2017) with flash-all.bat follow the instruction here https://developers.google.com/android/images but it remains the same. I read on Nexus Community that Google developers released images that fix signal problems from Feb 2017. I'm downloading this 7.1.1 (NMF26F, Dec 2016. All carriers except Verizon) and will give it a try even when it was released on Dec 2016.
tbmoc96 said:
Thank you guys and sorry for not saying, I flashed both 7.1.1 (NUF26N, Mar 2017, Verizon Only) and 7.1.2 (N2G47O, May 2017) with flash-all.bat follow the instruction here https://developers.google.com/android/images but it remains the same. I read on Nexus Community that Google developers released images that fix signal problems from Feb 2017. I'm downloading this 7.1.1 (NMF26F, Dec 2016. All carriers except Verizon) and will give it a try even when it was released on Dec 2016.
Click to expand...
Click to collapse
Again try relock on the boot loader and tell me if it helps
Sent from my Pixel XL using Tapatalk
tbmoc96 said:
Thank you guys and sorry for not saying, I flashed both 7.1.1 (NUF26N, Mar 2017, Verizon Only) and 7.1.2 (N2G47O, May 2017) with flash-all.bat follow the instruction here https://developers.google.com/android/images but it remains the same. I read on Nexus Community that Google developers released images that fix signal problems from Feb 2017. I'm downloading this 7.1.1 (NMF26F, Dec 2016. All carriers except Verizon) and will give it a try even when it was released on Dec 2016.
Click to expand...
Click to collapse
Hope you will fix it, if you got no success may you try flashing back to 6.0.0
Edit: check you imei, I will hope for you it doesn't show 0, then may you're f****d without a backup of your efs partition.
bennyboy2120 said:
Again try relock on the boot loader and tell me if it helps
Click to expand...
Click to collapse
The guide has the re-lock part so I'm 100% sure I tried to re-lock the bootloader. Not only the Google guide but on other topics on xda and Nexus Community someone re-locked the bootloader and they fixed the problem. Therefor, I followed them to re-lock but still no service
coremania said:
Hope you will fix it, if you got no success may you try flashing back to 6.0.0
Click to expand...
Click to collapse
I also tried to flash back to 6.0.0 first release firmware and 6.0.1 to get vendor for chroma / purenexus , still the same
coremania said:
Hope you will fix it, if you got no success may you try flashing back to 6.0.0
Edit: check you imei, I will hope for you it doesn't show 0, then may you're f****d without a backup of your efs partition.
Click to expand...
Click to collapse
My imei still there, I also have EFS backup ;(
tbmoc96 said:
My imei still there, I also have EFS backup ;(
Click to expand...
Click to collapse
I guess you flashed the backup, apn reset? Or flashing lineage?
Edit: take a look here, maybe deleting via fastboot and restoring with twrp will help
http://www.theandroidsoul.com/fix-e...d-wifibluetooth-issues-restoring-twrp-backup/
Sadly this problem ends up to hardware on other threads, hoping not for you
coremania said:
I guess you flashed the backup, apn reset? Or flashing lineage?
Edit: take a look here, maybe deleting via fastboot and restoring with twrp will help
http://www.theandroidsoul.com/fix-e...d-wifibluetooth-issues-restoring-twrp-backup/
Sadly this problem ends up to hardware on other threads, hoping not for you
Click to expand...
Click to collapse
I lost the network right after I upgraded my phone through OTA ;( I flashed stock firmware right after that so I guess it's not come from EFS partition. I backed up all things with TWRP after I had finished the flash-all.bat process. I'm checking out the thread, maybe there's a way out?
Yesterday I brought my phone to Huawei service center in my country but they don't officially sell the Nexus 6P in my country so they didn't take the phone because they don't have anything to fix its problem.
I would try, seems that you got nothing to loose
I'm having the same problem.
I've tried everything you did and when I select automatic bands in 4636 it does successfully, but still no signal.
Also, when I search for network in the mobile settings it always error.
I noticed that my GPS also stopped working. I only can use apps like Maps if I'm connected to a Wi-Fi.
Since the GPS stopped working this makes me believe it's an antenna problem.
If I selected WDCMA Only my network goes to Global instead of what I've selected.
I have the xt1511 (US Nexus Version), but since Nexus is always unlocked I know it isn't a CDMA/GSM trouble.
My wife's 6P started doing this about a month ago where she would randomly lose service for a minute. Today she lost it completely and it seems like there is an issue internally with the radio. I've tried multiple sim cards, factory resets, flashing the latest factory image, trying an old radio version etc. It seems like there has to be some kind of defect. I would hang on to the phone just in case there ends up being a class action lawsuit. Her phone is exactly one year and one month old.
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing...
Now what?, we dont know if its a hardware problem or is it a software one.
Should I take it to a service center in the us? I have no warranty.
Update 06-12-17: so i kept readying and I saw someone solved the issue installing a factory image from febuary. I did it flashed it, then went into recovery and made factory reset. and it worked!!!! signal is backkkk! im soo happy!!!
Update 2 06-12-17: yeah i was happy, and soo i was going back to normal, i installed twrp, and root, phone boot up and again bye bye signal.
Update 06-14-17: Turns out that since I got to Colombia a month ago, this country has like a national IMEI list. Since I didn't subscribe my device the carrier blowies my phone and that why I had no service... Soo this ends my journey with the no service problem. They fixed it
Humanreflect said:
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing... Now what?, we dont know if its a hardware problem or is it a software one. Should I take it to a service center in the us? I have no warranty.
Click to expand...
Click to collapse
Is your phone a H1511 or 1512? You didn't mention it explicitly but you may have changed the LTE bands using a hidden menu. Apparently this is a known bug with the hidden menu itself. Several people have had luck flashing an older version of Chroma and switching the band back to Auto. There is a link to the ROM for the 6P in this Nexus Help Forum. If you never used this menu before, you may just be able to access the menu and try setting to Auto first before flashing the ROM. You should get a confirmation that AUTO mode is selected. You also didn't explicitly mention whether the phone worked properly for a while AFTER your battery repair, OR was a direct result of your repair... which could mean it was damaged.
v12xke said:
Is your phone a H1511 or 1512? You didn't mention it explicitly but you may have changed the LTE bands using a hidden menu. Apparently this is a known bug with the hidden menu itself. Several people have had luck flashing an older version of Chroma and switching the band back to Auto. There is a link to the ROM for the 6P in this Nexus Help Forum. If you never used this menu before, you may just be able to access the menu and try setting to Auto first before flashing the ROM. You should get a confirmation that AUTO mode is selected. You also didn't explicitly mention whether the phone worked properly for a while AFTER your battery repair, OR was a direct result of your repair... which could mean it was damaged.
Click to expand...
Click to collapse
In my case I have a 1511 and I've tried this Chroma fix. No success.
v12xke said:
Is your phone a H1511 or 1512? You didn't mention it explicitly but you may have changed the LTE bands using a hidden menu. Apparently this is a known bug with the hidden menu itself. Several people have had luck flashing an older version of Chroma and switching the band back to Auto. There is a link to the ROM for the 6P in this Nexus Help Forum. If you never used this menu before, you may just be able to access the menu and try setting to Auto first before flashing the ROM. You should get a confirmation that AUTO mode is selected. You also didn't explicitly mention whether the phone worked properly for a while AFTER your battery repair, OR was a direct result of your repair... which could mean it was damaged.
Click to expand...
Click to collapse
its the 1511 version. Yes the phone worked perfectly after the repair. I was in the US, and three weeks ago I came to colombia. Suddenly it stoped working a couple of days again. I tried the chroma rom. Selected the Auto band. but it did nothing, rebooted and everything but didnt work.
Earlier today i installed a older factory image and it work, i thought it was solved, then i flashed twrp, rooted and lost service again... tried the factory images again and nothing...
Humanreflect said:
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing...
Now what?, we dont know if its a hardware problem or is it a software one.
Should I take it to a service center in the us? I have no warranty.
Update 06-12-17: so i kept readying and I saw someone solved the issue installing a factory image from febuary. I did it flashed it, then went into recovery and made factory reset. and it worked!!!! signal is backkkk! im soo happy!!!
Update 2 06-12-17: yeah i was happy, and soo i was going back to normal, i installed twrp, and root, phone boot up and again bye bye signal.
Update 06-14-17: Turns out that since I got to Colombia a month ago, this country has like a national IMEI list. Since I didn't subscribe my device the carrier blowies my phone and that why I had no service... Soo this ends my journey with the no service problem. They fixed it
Click to expand...
Click to collapse
Well, I've just checked your latest update today.
What did you do to include your device in this national list? And how did you find out about this list? I need to check if Brazil has it as well. Do you still have signal without problem?
Thanks.
Debuffer said:
Well, I've just checked your latest update today.
What did you do to include your device in this national list? And how did you find out about this list? I need to check if Brazil has it as well. Do you still have signal without problem?
Thanks.
Click to expand...
Click to collapse
Hey, i went to my carrier. And they tol me it was blocked. And they un blocked it.
It was imei blocked because ut wasebt in that imei national list. Soo it didnt work with any carrier.
you've fixed your phone
Humanreflect said:
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing...
Now what?, we dont know if its a hardware problem or is it a software one.
Should I take it to a service center in the us? I have no warranty.
Update 06-12-17: so i kept readying and I saw someone solved the issue installing a factory image from febuary. I did it flashed it, then went into recovery and made factory reset. and it worked!!!! signal is backkkk! im soo happy!!!
Update 2 06-12-17: yeah i was happy, and soo i was going back to normal, i installed twrp, and root, phone boot up and again bye bye signal.
Update 06-14-17: Turns out that since I got to Colombia a month ago, this country has like a national IMEI list. Since I didn't subscribe my device the carrier blowies my phone and that why I had no service... Soo this ends my journey with the no service problem. They fixed it
Click to expand...
Click to collapse
I can not have a case if you are not resolve. Im vietnames my english very bad sory!. Help me
Greetings Folks
I have a N910C and as mentioned in title recently I got stuck in to this issue
How it happened
I had CF-Rooted my phone and Odin flashed TWRP for custom ROMS so I tried a few and was not getting the perfomance thought SimplROM would do it for me in order to install that ROM it said in instructions to install latest Modem and Bootloader
So i tried downloading the ones given in v6C BL was downloaded but CP kept on giving me errors getting stuck at 7% on mega so being stupid I downloaded DPCB(MODEM) While ROM was offering DPK4
So everything went fine until after boot I realized am facing Not Registered to Network
Since I had experienced this before on other phone I went ASAP in dialer to check my IMEI & SN both are still intact
I knew about EFS unfortunately I backed it up on Phone Storage which was wiped for ROM and I forgot (So dont have EFS Backup )
I do recall years ago back when I had S3 I experienced this and sometimes flashing different firmware(CSC ,Modem) fixed it
What I have tried so far
I have already tried several stock ROMs most of em had DPI1 Baseband except 2 other ROMS no luck
tried combination file method too (the one that helps downgrade to kitkat i believe ) no luck
Tried XEO repair Firmware no luck
any suggestions ??
and on that contrary now that I am not on stock is there any way to find out which CSC and Stock ROM this phone originally was one or came with with IMEI or Serial I believe ?
Thanks in Advance
Anyone??
under the battery there's the serial number
install on your pc samsung smart switch program
run it with option of emergency software recovery - device initialisation
input the model of your phone
input the serial number
start
have patience and a good connection
your phone will (eventually) get the latest official firmware
https://www.blogtechtips.com/2017/06/24/easily-restore-samsung-device-firmware-with-smart-switch/
at least you'll have a working phone with stock rom
from here on you can try again and get informed better on what to do
good luck
w41ru5 said:
under the battery there's the serial number
install on your pc samsung smart switch program
run it with option of emergency software recovery - device initialisation
input the model of your phone
input the serial number
start
have patience and a good connection
your phone will (eventually) get the latest official firmware
https://www.blogtechtips.com/2017/06/24/easily-restore-samsung-device-firmware-with-smart-switch/
at least you'll have a working phone with stock rom
from here on you can try again and get informed better on what to do
good luck
Click to expand...
Click to collapse
Hey there bud I have almost tried most of fixes I could I'll give Smart Switch a try as I recall I checked before it didn't have initialization just the recovery mode, while in Kies 3 I did try initialization method by model and SN but it prompted device doesn't support initialization
Anyways do you think it could fix network?
Sent from my Pixel 2 XL using Tapatalk
crossmedia said:
Hey there bud I have almost tried most of fixes I could I'll give Smart Switch a try as I recall I checked before it didn't have initialization just the recovery mode, while in Kies 3 I did try initialization method by model and SN but it prompted device doesn't support initialization
Anyways do you think it could fix network?
Click to expand...
Click to collapse
Maybe restore the efs from recovery, if you have a backup that was working.
w41ru5 said:
Maybe restore the efs from recovery, if you have a backup that was working.
Click to expand...
Click to collapse
Jist checked not getting initialization option on smart switch ill see a work around it if its a version thing , as for working backup I lost it mate it was in twrp folder in phone storage it got wiped recovery softwares out there only help recovering media mostly if mass storage mount was option could have tried recovering for PC but that has been long gone since ICS
Sent from my Pixel 2 XL using Tapatalk
Yep. Same problem as mine. Im kinda lost now since i dont have anything; even in stock rom it cannot go beyond connecting to my carrier. It only able to read my contact.
Im guessing its a motherboard problem? Isnt it @w41ru5?
VannM said:
Yep. Same problem as mine. Im kinda lost now since i dont have anything; even in stock rom it cannot go beyond connecting to my carrier. It only able to read my contact.
Im guessing its a motherboard problem? Isnt it @w41ru5?
Click to expand...
Click to collapse
I don't know. Usually it's a modem issue when not recognizing the sim.
If it's a 910F snapdragon it might be the infamous eMMC issue.
If you have an EFS backup try to restore it from recovery TWRP.
Assuming its modem problem, its related to motherboard i guess, right?
Finally got the phone working, only to discovered that SIM not working. Really wasting my time and hype!
Plus, its hard to search for n910c replacement board here.
VannM said:
Assuming its modem problem, its related to motherboard i guess, right?
Finally got the phone working, only to discovered that SIM not working. Really wasting my time and hype!
Plus, its hard to search for n910c replacement board here.
Click to expand...
Click to collapse
The firmware, not the physical one.
Did you try to flash the 4 files repair firmware?
This is an example, I don't know what phone you have
https://firmware.gem-flash.com/index.php?a=downloads&b=folder&id=7081
Did you try the SmartSwitch pc program?
"...4 file repair..."- what? Ive google it until im almost run out of data here and you have a possible solution? You must be active in note4 forum.
One thing i noticed that, the IMEI and Serial Number are different from the sticker included.
I will try it, but not immediately; waiting for thurday-friday for data renewal.
My phone is n910c
EDIT : just checked the page you gave. I have few question;
What should i do with the files? What are the step? What are the program needed?
Is it related to SmartSwitch as you mention; need to use it?
Thanks!
VannM said:
"...4 file repair..."- what? Ive google it until im almost run out of data here and you have a possible solution? You must be active in note4 forum.
One thing i noticed that, the IMEI and Serial Number are different from the sticker included.
I will try it, but not immediately; waiting for thurday-friday for data renewal.
My phone is n910c
EDIT : just checked the page you gave. I have few question;
What should i do with the files? What are the step? What are the program needed?
Is it related to SmartSwitch as you mention; need to use it?
Thanks!
Click to expand...
Click to collapse
1. It's good you still have the IMEI. Not so important if they're different from the sticker. Where did you buy the phone from?
2. So if you go to check the 4 files repair, you need to search on that site the files for a 910C.
3. Did the phone worked on your country provider? If yes, maybe you need to search for the 4files corresponding to your region code.
4. These 4files have to be flashed with Odin
https://zfirmware.com/download-samsung-repair-firmwares/
5. SmartSwitch is an alternative to get the latest firmware for your phone according with the model and serial number.
https://www.sammobile.com/forum/threads/29914-SmartSwitch-Install-amp-update-or-replace-firmware
the "firmware.gem" are useless. the error says i need another package (i assume a quota) to download the needed files.
im currently testing "zfirmware", but have a doubt since it only give 1 type file (which country is it i dunno). but yeah, since my phone like that, it wouldnt hurt to try
EDIT : yep, nothing changed. the device not even bricked.
VannM said:
the "firmware.gem" are useless. the error says i need another package (i assume a quota) to download the needed files.
im currently testing "zfirmware", but have a doubt since it only give 1 type file (which country is it i dunno). but yeah, since my phone like that, it wouldnt hurt to try
EDIT : yep, nothing changed. the device not even bricked.
Click to expand...
Click to collapse
If something does not work, why do you give up so easy?
http://www.mediafire.com/file/a2fdo0xm9nat5jt/N910CXXS2DPJ3_N910CZTO2DPE2_ZTO.zip - this is marshmallow
https://androidfilehost.com/?fid=24269982087001472 - this is for lolipop
Put the phone in download mode, open Odin and try.
And try the smartswitch also.
w41ru5 said:
If something does not work, why do you give up so easy?
Click to expand...
Click to collapse
That hurts. A lot. Explanation below.
w41ru5 said:
http://www.mediafire.com/file/a2fdo0xm9nat5jt/N910CXXS2DPJ3_N910CZTO2DPE2_ZTO.zip - this is marshmallow
https://androidfilehost.com/?fid=24269982087001472 - this is for lolipop
Put the phone in download mode, open Odin and try.
And try the smartswitch also.
Click to expand...
Click to collapse
I tried files from LP and MM. It didnt work. And also smartswitch.
I was hoping that it will brick the phone (if i ever missed a step or incorrect file) but it didnt.
Might as well try looking for replacement board (or even a refurbished note4).
Thanks though for the suggestion @w41ru5!
Greetings again folks reading your replies above I have been trying almost every fix there is out there
First of all about Emergency Calls Only/Not Registered on Network
It can be due to several causes its can be Hardware ie faulty modem
it can be bad network coverage
it can be bad simcard
it can be SW with EFS problems or maybe even on rare occasion a modem file that you flashed
EFS can be either bad IMEI with CERT : FAIL or Just Network with IMEI and SN intact
just dial *#0011*# and see if you have CERT : PASS ( also someone with good IMEI/CERT and working network can share screenshot so i can compare whats wrong)
I am certain mine is EFS related because it happened after flashing modem DPCB modem via ODIN (I had TWRP EFS backup but the blunder I made was backing it up on phone storage and being careless forgot it was there and was wiped for custom ROM flashing process)
So far what I have tried
Combination File Method (and even downgrade to KK 4.4.4 )
Repair Firmware that include AP,BL,CP,CSC and even PIT
Kies 3 or Older Smart Switch says (Device doesn't support initialization ) since initialization feature was removed by Samsung on newer Smartswitch(since it was being used for wrong reasons? read somewhere)
Several different firmware's
OTA update
My IMEI CERT says PASS if only we had a network patch like Ariza Patch (for Galaxy S3) for Note 4 then we would be in luck so far at this point I dont think flashing ROM's would even help with bad EFS our only luck is Box e.g Z3x or Octo dont know if we are allowed to talk about those here (ill edit post if not)
these box applications have Network Patch for most Samsung models but I don't see one for N910C in most versions
for those with bad IMEI they can try writing good cert or efs on note 4 since they have already lost it I am sitting on it because my EFS is good on that part and for some reason box app isnt allowing me to back up my CERT if I am able to back up current cert then ill give those a try but I would prefer current IMEI since in my country IMEI should be verified to use the phone or you have to pay tax
I know its Bad EFS for sure because using Box application I chose reset EFS(after backing up current faulty EFS with good IMEI) upon reboot phone's imei was changed with no SN network came back for few seconds then gone again ,this happened to many users that have tried resetting EFS so I restored my original EFS
if anyone here with N910C and root can give me EFS folder I can corelate if any file required for network is missing since i have good IMEI
Cheers!
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.